Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc93e91ca42e475e7f5e1bd46274d40cd33f09f051724a086b331415aeee398b

Tx prefix hash: 54a40f0d1ea7bf7bd09aedec2bcdce8ade7dc0908f75b8caa4ac7dee238907d3
Tx public key: 240849cbbe221273d49356a84a7ab0cf517e03e9322fd64d24ba23d33fc1fb4e
Timestamp: 1716574147 Timestamp [UCT]: 2024-05-24 18:09:07 Age [y:d:h:m:s]: 00:300:02:19:53
Block: 1029159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214494 RingCT/type: yes/0
Extra: 01240849cbbe221273d49356a84a7ab0cf517e03e9322fd64d24ba23d33fc1fb4e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1131c54d899171133a6548c1f0f60162ee98b8b6169f76fe4d281f67ecc0fa3 0.600000000000 1497164 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": 1029169, "vin": [ { "gen": { "height": 1029159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1131c54d899171133a6548c1f0f60162ee98b8b6169f76fe4d281f67ecc0fa3" } } ], "extra": [ 1, 36, 8, 73, 203, 190, 34, 18, 115, 212, 147, 86, 168, 74, 122, 176, 207, 81, 126, 3, 233, 50, 47, 214, 77, 36, 186, 35, 211, 63, 193, 251, 78, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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