Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c70dff94fe354d4b146792de89d657c2ae18bb4bd123289c7db0967d8d8e18

Tx prefix hash: 0f981688b8265fbf2ff2866e309260a5f5d2660f6786692dd6d41faa53b75a5b
Tx public key: 2af56f205e7eaf04ad579f0a4dcafc9c431524a859a493ddab52193a0c187ca7
Timestamp: 1635585364 Timestamp [UCT]: 2021-10-30 09:16:04 Age [y:d:h:m:s]: 03:181:12:00:48
Block: 363542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 908017 RingCT/type: yes/0
Extra: 012af56f205e7eaf04ad579f0a4dcafc9c431524a859a493ddab52193a0c187ca70211000000074a0f5013000000000000000000

1 output(s) for total of 38.320824467000 dcy

stealth address amount amount idx
00: 46601e62629ae7c0f64d7515503a80c1e477e9bed19f5b5b3794f2c94c82031d 38.320824467000 738842 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": 363552, "vin": [ { "gen": { "height": 363542 } } ], "vout": [ { "amount": 38320824467, "target": { "key": "46601e62629ae7c0f64d7515503a80c1e477e9bed19f5b5b3794f2c94c82031d" } } ], "extra": [ 1, 42, 245, 111, 32, 94, 126, 175, 4, 173, 87, 159, 10, 77, 202, 252, 156, 67, 21, 36, 168, 89, 164, 147, 221, 171, 82, 25, 58, 12, 24, 124, 167, 2, 17, 0, 0, 0, 7, 74, 15, 80, 19, 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