Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99365c9d57d12cfbed2e1017ca27376d42c42c4df673d2a94a76b325498ca59d

Tx prefix hash: c4dce3a889084dbd7b3a5e1783b56d6929377f2d3367c2e753d20052b5bf5a29
Tx public key: 93804c503f2dcd33fe76b0b5e05d10cc069a9efde84350d8b6534e25b7d43cd7
Timestamp: 1627664858 Timestamp [UCT]: 2021-07-30 17:07:38 Age [y:d:h:m:s]: 03:121:01:45:18
Block: 303981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859044 RingCT/type: yes/0
Extra: 0193804c503f2dcd33fe76b0b5e05d10cc069a9efde84350d8b6534e25b7d43cd702110000002458045e5b000000000000000000

1 output(s) for total of 60.365005306000 dcy

stealth address amount amount idx
00: 9e5a0fe9d3e7147b2b33f2cec47a91ef34cc3dc369218408d8efab21c54428d4 60.365005306000 634358 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": 303991, "vin": [ { "gen": { "height": 303981 } } ], "vout": [ { "amount": 60365005306, "target": { "key": "9e5a0fe9d3e7147b2b33f2cec47a91ef34cc3dc369218408d8efab21c54428d4" } } ], "extra": [ 1, 147, 128, 76, 80, 63, 45, 205, 51, 254, 118, 176, 181, 224, 93, 16, 204, 6, 154, 158, 253, 232, 67, 80, 216, 182, 83, 78, 37, 183, 212, 60, 215, 2, 17, 0, 0, 0, 36, 88, 4, 94, 91, 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