Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89300d983038c85b166a4939cc089298abc3074e2cd384495d8688997675762b

Tx prefix hash: 5407c613d3e1f54d4c5ea3f39cae1cefe19e2d484ab51b594921552e8a3d8ffc
Tx public key: 938755c0bf55a7759198f90285b3c98f482a4931a0d0e05270e0e5c5272c3a2b
Timestamp: 1732803445 Timestamp [UCT]: 2024-11-28 14:17:25 Age [y:d:h:m:s]: 00:134:05:15:41
Block: 1163610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95737 RingCT/type: yes/0
Extra: 01938755c0bf55a7759198f90285b3c98f482a4931a0d0e05270e0e5c5272c3a2b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37f4b55de7976e91958ddf51f1b0e6b70f66b79b5b08dd7e1bf85eb0dc838240 0.600000000000 1649277 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": 1163620, "vin": [ { "gen": { "height": 1163610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37f4b55de7976e91958ddf51f1b0e6b70f66b79b5b08dd7e1bf85eb0dc838240" } } ], "extra": [ 1, 147, 135, 85, 192, 191, 85, 167, 117, 145, 152, 249, 2, 133, 179, 201, 143, 72, 42, 73, 49, 160, 208, 224, 82, 112, 224, 229, 197, 39, 44, 58, 43, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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