Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c87cb5e62f40b6f59181ae4e495f712d5b21e09f1961d468861a74e112588a2

Tx prefix hash: 5386a99987b5a81cc4866a9e61c5c240656dc028a36b9c6902368ad8073e8923
Tx public key: ac203d5dc3ece27b0efd4cf4eee5fdf17b03a9e1c8092642b6495386bedc6978
Timestamp: 1731039962 Timestamp [UCT]: 2024-11-08 04:26:02 Age [y:d:h:m:s]: 00:132:23:02:09
Block: 1149001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94863 RingCT/type: yes/0
Extra: 01ac203d5dc3ece27b0efd4cf4eee5fdf17b03a9e1c8092642b6495386bedc6978021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d572e49574d3ed518cc0323d1884a6f2d1b55d3ef414fb5849833b7b8523c6ab 0.600000000000 1633980 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": 1149011, "vin": [ { "gen": { "height": 1149001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d572e49574d3ed518cc0323d1884a6f2d1b55d3ef414fb5849833b7b8523c6ab" } } ], "extra": [ 1, 172, 32, 61, 93, 195, 236, 226, 123, 14, 253, 76, 244, 238, 229, 253, 241, 123, 3, 169, 225, 200, 9, 38, 66, 182, 73, 83, 134, 190, 220, 105, 120, 2, 17, 0, 0, 0, 1, 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