Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74947738a1d02ad76d5e492b718248df78fa8e5bee2799a9b5992fbacd1e4ed9

Tx prefix hash: cd7446d3200ac623477d25b1ba07f5d39b04a5d9982d2ca9f45b025ee89c3b8d
Tx public key: a54a7c5f33cc29aec13aa4a5ce5c44eafcd170ce858d38812d728ac99cd11f40
Timestamp: 1710888313 Timestamp [UCT]: 2024-03-19 22:45:13 Age [y:d:h:m:s]: 01:017:21:07:39
Block: 982033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273732 RingCT/type: yes/0
Extra: 01a54a7c5f33cc29aec13aa4a5ce5c44eafcd170ce858d38812d728ac99cd11f4002110000001252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 183f4061d79e48965c893a8241dc9955bcec6162b3eacf7efbd3160fea0274ca 0.600000000000 1442136 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": 982043, "vin": [ { "gen": { "height": 982033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "183f4061d79e48965c893a8241dc9955bcec6162b3eacf7efbd3160fea0274ca" } } ], "extra": [ 1, 165, 74, 124, 95, 51, 204, 41, 174, 193, 58, 164, 165, 206, 92, 68, 234, 252, 209, 112, 206, 133, 141, 56, 129, 45, 114, 138, 201, 156, 209, 31, 64, 2, 17, 0, 0, 0, 18, 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