Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a8a471eb223af7ffe9895d4b5535a28d33229137395843ed36e8963748eb092

Tx prefix hash: e39d4f2fd50e7d2d5e46b6fd5e240c4667e78ceb5b8ddc49d3b905a181ab026f
Tx public key: 081d396cd27e76c282412346fb26e86a5f8c721ea04824a5b94fb048dd301c37
Timestamp: 1716845815 Timestamp [UCT]: 2024-05-27 21:36:55 Age [y:d:h:m:s]: 00:304:02:26:37
Block: 1031414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217321 RingCT/type: yes/0
Extra: 01081d396cd27e76c282412346fb26e86a5f8c721ea04824a5b94fb048dd301c370211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56dac0fd30935c01635bb6cf79b6d54b4b2c990f64f580d073b224fbdebe977b 0.600000000000 1499855 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": 1031424, "vin": [ { "gen": { "height": 1031414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56dac0fd30935c01635bb6cf79b6d54b4b2c990f64f580d073b224fbdebe977b" } } ], "extra": [ 1, 8, 29, 57, 108, 210, 126, 118, 194, 130, 65, 35, 70, 251, 38, 232, 106, 95, 140, 114, 30, 160, 72, 36, 165, 185, 79, 176, 72, 221, 48, 28, 55, 2, 17, 0, 0, 0, 2, 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