Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d7d9bd2adc0665c7b9b53bec4c647e51c9cd3811a62bc90be898030d5e6d43

Tx prefix hash: 3e9ddba16854f25d5324551f50c7c124b1b87a3cafbe48935d6a3f428472a6d2
Tx public key: 5d23404f260aa22dc1e94dbd46a9d1aad01c1b986691247ffeadf4cdfba0ba65
Timestamp: 1631603397 Timestamp [UCT]: 2021-09-14 07:09:57 Age [y:d:h:m:s]: 04:051:22:19:01
Block: 333480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1071096 RingCT/type: yes/0
Extra: 015d23404f260aa22dc1e94dbd46a9d1aad01c1b986691247ffeadf4cdfba0ba6502110000001bf29d7abf000000000000000000

1 output(s) for total of 48.199525995000 dcy

stealth address amount amount idx
00: 845c7908717752fba8b03b42da88d808ca75d1563ce678b9082ee8ca10f0aacf 48.199525995000 688133 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": 333490, "vin": [ { "gen": { "height": 333480 } } ], "vout": [ { "amount": 48199525995, "target": { "key": "845c7908717752fba8b03b42da88d808ca75d1563ce678b9082ee8ca10f0aacf" } } ], "extra": [ 1, 93, 35, 64, 79, 38, 10, 162, 45, 193, 233, 77, 189, 70, 169, 209, 170, 208, 28, 27, 152, 102, 145, 36, 127, 254, 173, 244, 205, 251, 160, 186, 101, 2, 17, 0, 0, 0, 27, 242, 157, 122, 191, 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