Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f9cae7524809d15609b07c1ae8f697a0bdedd72a1d7319ecf75c9014ea1d65a

Tx prefix hash: 99701bc2175252e87b184ca345f5510deb3b3e2b7048a662516dc77077800dd6
Tx public key: b0d124037fd92de67bc7e4e04699ef09637a8fd3fd5296869075eb0a0587da07
Timestamp: 1737106630 Timestamp [UCT]: 2025-01-17 09:37:10 Age [y:d:h:m:s]: 00:308:04:57:12
Block: 1199229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217779 RingCT/type: yes/0
Extra: 01b0d124037fd92de67bc7e4e04699ef09637a8fd3fd5296869075eb0a0587da07021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fc7fa632024b9afb57396e96b5d047fd5f4f54a68d58d488e0dd5436f8499df 0.600000000000 1685858 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": 1199239, "vin": [ { "gen": { "height": 1199229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fc7fa632024b9afb57396e96b5d047fd5f4f54a68d58d488e0dd5436f8499df" } } ], "extra": [ 1, 176, 209, 36, 3, 127, 217, 45, 230, 123, 199, 228, 224, 70, 153, 239, 9, 99, 122, 143, 211, 253, 82, 150, 134, 144, 117, 235, 10, 5, 135, 218, 7, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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