Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d745b9c3e164002dc88b00f1ff1e01bed8abc376b95e6140afc52d09b68cb3

Tx prefix hash: 57c17b54032e1cecb8bb8626ab00b1412337a0b45831515f4d522c9c355940f4
Tx public key: 8304daad81087c093c3ed4db7e97934ef5142d9113420f35ab61dbd9d054dc52
Timestamp: 1708493153 Timestamp [UCT]: 2024-02-21 05:25:53 Age [y:d:h:m:s]: 01:048:09:07:53
Block: 962159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295605 RingCT/type: yes/0
Extra: 018304daad81087c093c3ed4db7e97934ef5142d9113420f35ab61dbd9d054dc52021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4dd2437a98434afd4f85d40b73bd6f0d23415a08f44e8fc9a445fa2be607226 0.600000000000 1421782 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": 962169, "vin": [ { "gen": { "height": 962159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4dd2437a98434afd4f85d40b73bd6f0d23415a08f44e8fc9a445fa2be607226" } } ], "extra": [ 1, 131, 4, 218, 173, 129, 8, 124, 9, 60, 62, 212, 219, 126, 151, 147, 78, 245, 20, 45, 145, 19, 66, 15, 53, 171, 97, 219, 217, 208, 84, 220, 82, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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