Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4651ad04c7e4ed3df7904aff10975728eac3e57478763f9a3976ac98976db605

Tx prefix hash: e5e57b8623513772af4208db12627a896f47a6581a488a1aeb2098c2f5fc1f1b
Tx public key: 652d3b88b172a0d0f375fa2e1f47bed1d4d2484f96402d5ec48191115b9602f5
Timestamp: 1583238395 Timestamp [UCT]: 2020-03-03 12:26:35 Age [y:d:h:m:s]: 04:298:12:18:46
Block: 75593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107641 RingCT/type: yes/0
Extra: 01652d3b88b172a0d0f375fa2e1f47bed1d4d2484f96402d5ec48191115b9602f50211000000068a2ee0d9000000000000000000

1 output(s) for total of 344.770268636000 dcy

stealth address amount amount idx
00: 03e8a2f92ec73f65cebeeb9f47cddf5f158961b84da71323b3a15afbb411a806 344.770268636000 139547 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": 75603, "vin": [ { "gen": { "height": 75593 } } ], "vout": [ { "amount": 344770268636, "target": { "key": "03e8a2f92ec73f65cebeeb9f47cddf5f158961b84da71323b3a15afbb411a806" } } ], "extra": [ 1, 101, 45, 59, 136, 177, 114, 160, 208, 243, 117, 250, 46, 31, 71, 190, 209, 212, 210, 72, 79, 150, 64, 45, 94, 196, 129, 145, 17, 91, 150, 2, 245, 2, 17, 0, 0, 0, 6, 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