Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 590d6d9920f743cdfd7dd2474a0f53df9535fe3cf329f4c8eb09b10e4253314a

Tx prefix hash: 9d2d2cfcfaf94a193a5be58fe852ae6d04e05274bfcfa59a87c6acaa52e78f4e
Tx public key: 6abd15b9f67831fd181489da92a23c64b0917a5928f1dad2c5996f0ce020f33f
Timestamp: 1761373714 Timestamp [UCT]: 2025-10-25 06:28:34 Age [y:d:h:m:s]: 00:074:22:54:56
Block: 1397461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53659 RingCT/type: yes/0
Extra: 016abd15b9f67831fd181489da92a23c64b0917a5928f1dad2c5996f0ce020f33f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131ce520dbfd379041ed58d05672133098fee85f057bcad6ed190c6604b1ec7c 0.600000000000 1885752 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": 1397471, "vin": [ { "gen": { "height": 1397461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131ce520dbfd379041ed58d05672133098fee85f057bcad6ed190c6604b1ec7c" } } ], "extra": [ 1, 106, 189, 21, 185, 246, 120, 49, 253, 24, 20, 137, 218, 146, 162, 60, 100, 176, 145, 122, 89, 40, 241, 218, 210, 197, 153, 111, 12, 224, 32, 243, 63, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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