Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83284741e73c4bddae63ec2ba9676ac4832df53e78e5eb7e36932261ef2b59a1

Tx prefix hash: 836513640e72cb82a310d947f2b33f0138935128ce2af4bc603de852b69b53ac
Tx public key: 568a53d0e4ff611a58b5fd99e7b9c602854cc7d96806aeb4845bef87f2e40320
Timestamp: 1718681127 Timestamp [UCT]: 2024-06-18 03:25:27 Age [y:d:h:m:s]: 00:286:05:12:46
Block: 1046620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204523 RingCT/type: yes/0
Extra: 01568a53d0e4ff611a58b5fd99e7b9c602854cc7d96806aeb4845bef87f2e40320021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae29e947667179b63b0a0277865653a9c75cb1c34b5d86496fe72d97033311c 0.600000000000 1516437 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": 1046630, "vin": [ { "gen": { "height": 1046620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae29e947667179b63b0a0277865653a9c75cb1c34b5d86496fe72d97033311c" } } ], "extra": [ 1, 86, 138, 83, 208, 228, 255, 97, 26, 88, 181, 253, 153, 231, 185, 198, 2, 133, 76, 199, 217, 104, 6, 174, 180, 132, 91, 239, 135, 242, 228, 3, 32, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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