Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ee2a8b74fc8d73bf86303460d593ba79803551a2cc5bd7f7a67a55ba711d37

Tx prefix hash: 73af34b15f35445879a708de188388d55a47ed3e5f23128766272421e1aa7b35
Tx public key: aa247e190080d697526a3e0601fab4f90678aea3753755f12a6363954f55d484
Timestamp: 1583686650 Timestamp [UCT]: 2020-03-08 16:57:30 Age [y:d:h:m:s]: 04:303:09:08:01
Block: 78819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111613 RingCT/type: yes/0
Extra: 01aa247e190080d697526a3e0601fab4f90678aea3753755f12a6363954f55d48402110000001c8a2ee0d9000000000000000000

1 output(s) for total of 336.388178597000 dcy

stealth address amount amount idx
00: a2d7a03925ed5efba0be124ca3a26267440e032bea584f0d16b924dfcc7d2255 336.388178597000 144393 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": 78829, "vin": [ { "gen": { "height": 78819 } } ], "vout": [ { "amount": 336388178597, "target": { "key": "a2d7a03925ed5efba0be124ca3a26267440e032bea584f0d16b924dfcc7d2255" } } ], "extra": [ 1, 170, 36, 126, 25, 0, 128, 214, 151, 82, 106, 62, 6, 1, 250, 180, 249, 6, 120, 174, 163, 117, 55, 85, 241, 42, 99, 99, 149, 79, 85, 212, 132, 2, 17, 0, 0, 0, 28, 138, 46, 224, 217, 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