Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ffd123dbe0b06ae22da425e57dca72d82fd61ea2c66a46f676c37c57065a433

Tx prefix hash: f695f560ed766f69061a88fb2c3651c10a345b88ab091fa450a19b28872d0bc9
Tx public key: ce4c04f961f1aa6e3b553a526c6bd67f1c98a81c3a5f063f3dcba5747969c53b
Timestamp: 1697129489 Timestamp [UCT]: 2023-10-12 16:51:29 Age [y:d:h:m:s]: 01:164:16:40:21
Block: 868159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378723 RingCT/type: yes/0
Extra: 01ce4c04f961f1aa6e3b553a526c6bd67f1c98a81c3a5f063f3dcba5747969c53b02110000000cfaf35c9c000000000000000000

1 output(s) for total of 0.815509216000 dcy

stealth address amount amount idx
00: 2c8db48ab83fb4476d2fd3606850bc9f26005d18c00119f845d0445826d0c390 0.815509216000 1322932 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": 868169, "vin": [ { "gen": { "height": 868159 } } ], "vout": [ { "amount": 815509216, "target": { "key": "2c8db48ab83fb4476d2fd3606850bc9f26005d18c00119f845d0445826d0c390" } } ], "extra": [ 1, 206, 76, 4, 249, 97, 241, 170, 110, 59, 85, 58, 82, 108, 107, 214, 127, 28, 152, 168, 28, 58, 95, 6, 63, 61, 203, 165, 116, 121, 105, 197, 59, 2, 17, 0, 0, 0, 12, 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