Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d218e7b1cb5c84cfd4b4e40400bdfc4f1f0486c9a0fdcac2c6a091edecd20d

Tx prefix hash: 9828dac4ed863b74233d703efe37bc99d1a4e27d55f242e8267b5731b412f758
Tx public key: 7858e2e1fb608978aef34c32001398aaca89166376f883e8e92c9f98d74792ba
Timestamp: 1713127222 Timestamp [UCT]: 2024-04-14 20:40:22 Age [y:d:h:m:s]: 00:280:02:43:49
Block: 1000558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200467 RingCT/type: yes/0
Extra: 017858e2e1fb608978aef34c32001398aaca89166376f883e8e92c9f98d74792ba02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b5c73c00672af30ba0b85e25d1162e5a0d801fe83883153ce1ff4223a3d1bed 0.600000000000 1461056 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": 1000568, "vin": [ { "gen": { "height": 1000558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b5c73c00672af30ba0b85e25d1162e5a0d801fe83883153ce1ff4223a3d1bed" } } ], "extra": [ 1, 120, 88, 226, 225, 251, 96, 137, 120, 174, 243, 76, 50, 0, 19, 152, 170, 202, 137, 22, 99, 118, 248, 131, 232, 233, 44, 159, 152, 215, 71, 146, 186, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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