Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f07bc9d5888e9dc8e756f38312a7ff8f26704d3192ffdd2c8fa4e418e7e7614

Tx prefix hash: 186021d81813efb8782bd0c8df1f9f464cd8fd43624ffc8150683d3c60c0c08d
Tx public key: a8a7cef02d1eb199c179bf12e5fb33ea2ef20b7502cedf87a957188543002a01
Timestamp: 1747655070 Timestamp [UCT]: 2025-05-19 11:44:30 Age [y:d:h:m:s]: 00:250:02:11:13
Block: 1286293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176353 RingCT/type: yes/0
Extra: 01a8a7cef02d1eb199c179bf12e5fb33ea2ef20b7502cedf87a957188543002a010211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1b198eccb1104444046abcb54024f13afdc2630e4d053e258a426ccd4e6f120 0.600000000000 1773758 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": 1286303, "vin": [ { "gen": { "height": 1286293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1b198eccb1104444046abcb54024f13afdc2630e4d053e258a426ccd4e6f120" } } ], "extra": [ 1, 168, 167, 206, 240, 45, 30, 177, 153, 193, 121, 191, 18, 229, 251, 51, 234, 46, 242, 11, 117, 2, 206, 223, 135, 169, 87, 24, 133, 67, 0, 42, 1, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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