Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f3d0f6dc912f2e1f1dcf6dcfae689f0af05666ba8cb506e4d321b0749c5193

Tx prefix hash: be1135c972043a7f0645c1022ef35eb305e954e416d51fb1f3ebdf0133c2b11d
Tx public key: a740a340ec0b4731a17408b2524862f7efa4cb3ea955df3c2d0a6b4b7e8108c7
Timestamp: 1736462480 Timestamp [UCT]: 2025-01-09 22:41:20 Age [y:d:h:m:s]: 00:096:03:17:55
Block: 1193902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68501 RingCT/type: yes/0
Extra: 01a740a340ec0b4731a17408b2524862f7efa4cb3ea955df3c2d0a6b4b7e8108c70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6690c5ba514fa352834a4481a4e862feb56ec39a6662b98bca7a28a23ccba88d 0.600000000000 1680467 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": 1193912, "vin": [ { "gen": { "height": 1193902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6690c5ba514fa352834a4481a4e862feb56ec39a6662b98bca7a28a23ccba88d" } } ], "extra": [ 1, 167, 64, 163, 64, 236, 11, 71, 49, 161, 116, 8, 178, 82, 72, 98, 247, 239, 164, 203, 62, 169, 85, 223, 60, 45, 10, 107, 75, 126, 129, 8, 199, 2, 17, 0, 0, 0, 3, 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