Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ff41b43ca841bc79586de410e08c651e95a1f39fc28cd0158aea13d1f0accfd

Tx prefix hash: ad43f1b4e04b8097dfc9fbc0706c663bf54d44d4b8d2ae6885b7739ea8813145
Tx public key: 107be4c2476e0f044bc74a1b31ff6c0da959e51f2477ccffefd7119f82296550
Timestamp: 1704408134 Timestamp [UCT]: 2024-01-04 22:42:14 Age [y:d:h:m:s]: 01:053:12:12:58
Block: 928268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299332 RingCT/type: yes/0
Extra: 01107be4c2476e0f044bc74a1b31ff6c0da959e51f2477ccffefd7119f8229655002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f4aec2fb67d2a6ad9d6c3c35c3166da7e1bbc4b206641b16011f69d9de15f09 0.600000000000 1386126 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": 928278, "vin": [ { "gen": { "height": 928268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f4aec2fb67d2a6ad9d6c3c35c3166da7e1bbc4b206641b16011f69d9de15f09" } } ], "extra": [ 1, 16, 123, 228, 194, 71, 110, 15, 4, 75, 199, 74, 27, 49, 255, 108, 13, 169, 89, 229, 31, 36, 119, 204, 255, 239, 215, 17, 159, 130, 41, 101, 80, 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