Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9898fdbb7e1058576794cac9d697a3f69a7c8652ecb90984148a9c2ae1f98737

Tx prefix hash: 5ca0970b1ad4c274dcfaadbaadefc460220a120652ff7c4b5a83ba60ec584b0b
Tx public key: 81413a9785491dc7c8da97143c9469f5ec7530e19eb1f054d7f62b9e4aef0312
Timestamp: 1720185842 Timestamp [UCT]: 2024-07-05 13:24:02 Age [y:d:h:m:s]: 00:277:17:54:35
Block: 1059092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198457 RingCT/type: yes/0
Extra: 0181413a9785491dc7c8da97143c9469f5ec7530e19eb1f054d7f62b9e4aef03120211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a92868a91a074233ce18c6aece875a9d1bf2076eba7e0fae5731af1b8c531088 0.600000000000 1529553 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": 1059102, "vin": [ { "gen": { "height": 1059092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a92868a91a074233ce18c6aece875a9d1bf2076eba7e0fae5731af1b8c531088" } } ], "extra": [ 1, 129, 65, 58, 151, 133, 73, 29, 199, 200, 218, 151, 20, 60, 148, 105, 245, 236, 117, 48, 225, 158, 177, 240, 84, 215, 246, 43, 158, 74, 239, 3, 18, 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