Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a360d6001d1db8d4d243222c05ec1f7dddf19530645a210b492f7dc8155d1c74

Tx prefix hash: 4b414726ac5abd46beb2bf04e681f0ab289a30a383164232226431430d5709a0
Tx public key: 7a2ae08e9a10cfbdb6e5d4bda4c8e9aff6a2b33c8c126fcb37c9ae15bdf4602e
Timestamp: 1734100967 Timestamp [UCT]: 2024-12-13 14:42:47 Age [y:d:h:m:s]: 00:101:19:24:00
Block: 1174373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72525 RingCT/type: yes/0
Extra: 017a2ae08e9a10cfbdb6e5d4bda4c8e9aff6a2b33c8c126fcb37c9ae15bdf4602e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0646f61b97857c15acd7d12783f6b73e10ec92a1da96da77f5b16343762371d9 0.600000000000 1660518 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": 1174383, "vin": [ { "gen": { "height": 1174373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0646f61b97857c15acd7d12783f6b73e10ec92a1da96da77f5b16343762371d9" } } ], "extra": [ 1, 122, 42, 224, 142, 154, 16, 207, 189, 182, 229, 212, 189, 164, 200, 233, 175, 246, 162, 179, 60, 140, 18, 111, 203, 55, 201, 174, 21, 189, 244, 96, 46, 2, 17, 0, 0, 0, 3, 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