Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 488e125d4888f7900e7303efe63fda8f24f67643a85941396c3d6643a9ad80df

Tx prefix hash: 54ca51a253ba2af9b67fcbc56fa6f6a74bec48e30e32d403519c7e83782587bd
Tx public key: d68e2740f9b0c900e6c63da563fb4f73da0a1ee8997437a96459d72cbd9248e2
Timestamp: 1737229195 Timestamp [UCT]: 2025-01-18 19:39:55 Age [y:d:h:m:s]: 00:150:19:53:37
Block: 1200212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107527 RingCT/type: yes/0
Extra: 01d68e2740f9b0c900e6c63da563fb4f73da0a1ee8997437a96459d72cbd9248e20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f042c98b8234a504542d622aa27c277a21e3d723e256bf312cd1ea3b8e1542f7 0.600000000000 1686855 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1200222, "vin": [ { "gen": { "height": 1200212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f042c98b8234a504542d622aa27c277a21e3d723e256bf312cd1ea3b8e1542f7" } } ], "extra": [ 1, 214, 142, 39, 64, 249, 176, 201, 0, 230, 198, 61, 165, 99, 251, 79, 115, 218, 10, 30, 232, 153, 116, 55, 169, 100, 89, 215, 44, 189, 146, 72, 226, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8