Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513e924264bd152a6701740ee379af6ceeef6b8ac5f5451734bcf4a1f2ab0bed

Tx prefix hash: 7be5a2dd4a731fa04841bcafdce321fe16613e7b43c9bd0ac33a69eb99598e95
Tx public key: 7d5930b1f6995dbddc20ce070c944478df7b4210c7e4de328c211df8474a47a4
Timestamp: 1696587909 Timestamp [UCT]: 2023-10-06 10:25:09 Age [y:d:h:m:s]: 01:175:03:02:24
Block: 863660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386197 RingCT/type: yes/0
Extra: 017d5930b1f6995dbddc20ce070c944478df7b4210c7e4de328c211df8474a47a4021100000001faf35c9c000000000000000000

1 output(s) for total of 0.843987344000 dcy

stealth address amount amount idx
00: 93cf51ff52fc3af1d45084160f328a0e1452e6d8b63de991686ca5c6523b9fc9 0.843987344000 1318134 of 0

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": 863670, "vin": [ { "gen": { "height": 863660 } } ], "vout": [ { "amount": 843987344, "target": { "key": "93cf51ff52fc3af1d45084160f328a0e1452e6d8b63de991686ca5c6523b9fc9" } } ], "extra": [ 1, 125, 89, 48, 177, 246, 153, 93, 189, 220, 32, 206, 7, 12, 148, 68, 120, 223, 123, 66, 16, 199, 228, 222, 50, 140, 33, 29, 248, 71, 74, 71, 164, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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