Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34560ac74c3d10e57e2fb72af93922e1f52df83e5aaae8123292ed1d35b24910

Tx prefix hash: ee8d7680875ea2b4e218ae9d72033aa04552b0c16160ed544ee6378664aa37dc
Tx public key: 3ae0896d159dbb98da082724a689f6778857c5b44d0e1d94f89125b47b04ddab
Timestamp: 1707230500 Timestamp [UCT]: 2024-02-06 14:41:40 Age [y:d:h:m:s]: 00:320:15:15:39
Block: 951676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229594 RingCT/type: yes/0
Extra: 013ae0896d159dbb98da082724a689f6778857c5b44d0e1d94f89125b47b04ddab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1eee1fc292ca4de479be093867e1cb69ea4aafe8d19586ffe0e43c6d68eaea5 0.600000000000 1410478 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": 951686, "vin": [ { "gen": { "height": 951676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1eee1fc292ca4de479be093867e1cb69ea4aafe8d19586ffe0e43c6d68eaea5" } } ], "extra": [ 1, 58, 224, 137, 109, 21, 157, 187, 152, 218, 8, 39, 36, 166, 137, 246, 119, 136, 87, 197, 180, 77, 14, 29, 148, 248, 145, 37, 180, 123, 4, 221, 171, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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