Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06fed6e312ee14ac58c5bea65a556859338b228d0aa805385d85054227780020

Tx prefix hash: cccc61e94a0c9f0e14574a54fd08f6717b7a2e8c74884ac7db48d98ea3f9e22e
Tx public key: a9bc9370d63c2acf11c9acf54067dc764effedc5f2cec7fcb9d47ae21706c1d4
Timestamp: 1698411902 Timestamp [UCT]: 2023-10-27 13:05:02 Age [y:d:h:m:s]: 01:189:02:06:04
Block: 878795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396150 RingCT/type: yes/0
Extra: 01a9bc9370d63c2acf11c9acf54067dc764effedc5f2cec7fcb9d47ae21706c1d40211000000024b8f5122000000000000000000

1 output(s) for total of 0.751957248000 dcy

stealth address amount amount idx
00: d2582949ceb8c64009af0a5b1cd9246416619e1c8df617e146e93f4d8d8b70c5 0.751957248000 1334275 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": 878805, "vin": [ { "gen": { "height": 878795 } } ], "vout": [ { "amount": 751957248, "target": { "key": "d2582949ceb8c64009af0a5b1cd9246416619e1c8df617e146e93f4d8d8b70c5" } } ], "extra": [ 1, 169, 188, 147, 112, 214, 60, 42, 207, 17, 201, 172, 245, 64, 103, 220, 118, 78, 255, 237, 197, 242, 206, 199, 252, 185, 212, 122, 226, 23, 6, 193, 212, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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