Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c34110860b90872e6ae0ebb056b3bf61f864ba00a75aa82766d2303c7398488

Tx prefix hash: ce2b95e95f546fd0815b305c3b2967c58e2af789f5c35ff26f8ecf00c5ca3206
Tx public key: 32ab2da9f6b58980398dd4a78f8a0a254f2ddc5847c692962c086a8453afcef4
Timestamp: 1702175020 Timestamp [UCT]: 2023-12-10 02:23:40 Age [y:d:h:m:s]: 01:038:09:23:54
Block: 909783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288794 RingCT/type: yes/0
Extra: 0132ab2da9f6b58980398dd4a78f8a0a254f2ddc5847c692962c086a8453afcef402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa499eb86a47849b286a05ff701eab242f7eb8eaadc34689bf98b3de7d2c0039 0.600000000000 1366904 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": 909793, "vin": [ { "gen": { "height": 909783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa499eb86a47849b286a05ff701eab242f7eb8eaadc34689bf98b3de7d2c0039" } } ], "extra": [ 1, 50, 171, 45, 169, 246, 181, 137, 128, 57, 141, 212, 167, 143, 138, 10, 37, 79, 45, 220, 88, 71, 198, 146, 150, 44, 8, 106, 132, 83, 175, 206, 244, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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