Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ac50def501f56977544076f5b9ef785d36e7367fbdad3b5f1bb1d8673017ae

Tx prefix hash: 496e5b3afb7de414715a6f3b08b55cf33c628ecd25d3288aeb98e5ae17e97103
Tx public key: 189818e41042fee036a750a77285a3841f3cd11b83bf1acf54adec1073d7cc36
Timestamp: 1706434531 Timestamp [UCT]: 2024-01-28 09:35:31 Age [y:d:h:m:s]: 01:141:10:14:22
Block: 945065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362092 RingCT/type: yes/0
Extra: 01189818e41042fee036a750a77285a3841f3cd11b83bf1acf54adec1073d7cc360211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d53e1f85245069a0817d562dca2d0b0c395214604de5e64eaa66a78d8f0067f 0.600000000000 1403373 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": 945075, "vin": [ { "gen": { "height": 945065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d53e1f85245069a0817d562dca2d0b0c395214604de5e64eaa66a78d8f0067f" } } ], "extra": [ 1, 24, 152, 24, 228, 16, 66, 254, 224, 54, 167, 80, 167, 114, 133, 163, 132, 31, 60, 209, 27, 131, 191, 26, 207, 84, 173, 236, 16, 115, 215, 204, 54, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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