Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe7cb6205778ef1ce569644f19b8cca4ac0d6715cfed66f6e48c737d47005fb7

Tx prefix hash: de825a844c975ada66f55040b947c1cf34d4d4c05fbb5842bb81fb657ffa4736
Tx public key: 64d182adfdb6e95c83dfe9565eeb7b3578e0f0a91775910d9361dc8043dbf771
Timestamp: 1634972175 Timestamp [UCT]: 2021-10-23 06:56:15 Age [y:d:h:m:s]: 03:038:13:55:32
Block: 358651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 805860 RingCT/type: yes/0
Extra: 0164d182adfdb6e95c83dfe9565eeb7b3578e0f0a91775910d9361dc8043dbf77102110000000cf29d7abf000000000000000000

1 output(s) for total of 39.777800456000 dcy

stealth address amount amount idx
00: dcb5f05a5cdc83a871eb77a0da206f91df1f25bca3a98775a8437c6d775b7705 39.777800456000 730684 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": 358661, "vin": [ { "gen": { "height": 358651 } } ], "vout": [ { "amount": 39777800456, "target": { "key": "dcb5f05a5cdc83a871eb77a0da206f91df1f25bca3a98775a8437c6d775b7705" } } ], "extra": [ 1, 100, 209, 130, 173, 253, 182, 233, 92, 131, 223, 233, 86, 94, 235, 123, 53, 120, 224, 240, 169, 23, 117, 145, 13, 147, 97, 220, 128, 67, 219, 247, 113, 2, 17, 0, 0, 0, 12, 242, 157, 122, 191, 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