Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a661f74b1019b63f35efef898031262d96b57085541df7f3e1f3d388d17e4626

Tx prefix hash: ec8d5e1433b804d251e30dc8eb97e5df8a2d7fa3eee29d8bba6b1fbcbccea47e
Tx public key: e0c1e8ec02cada830da7acd30bc126f8df262c45f568ec30fbfef677681aee33
Timestamp: 1717094233 Timestamp [UCT]: 2024-05-30 18:37:13 Age [y:d:h:m:s]: 00:153:19:00:02
Block: 1033468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110087 RingCT/type: yes/0
Extra: 01e0c1e8ec02cada830da7acd30bc126f8df262c45f568ec30fbfef677681aee330211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa4c35b9d5629baa7366514b8f11547ebdaccc30e5892c5897bbc533cca4bdfc 0.600000000000 1501935 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": 1033478, "vin": [ { "gen": { "height": 1033468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa4c35b9d5629baa7366514b8f11547ebdaccc30e5892c5897bbc533cca4bdfc" } } ], "extra": [ 1, 224, 193, 232, 236, 2, 202, 218, 131, 13, 167, 172, 211, 11, 193, 38, 248, 223, 38, 44, 69, 245, 104, 236, 48, 251, 254, 246, 119, 104, 26, 238, 51, 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