Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1a8eaea2fe9654dd577231b62c7ced0cb454070c5fc47a920a2064a8a31ced

Tx prefix hash: b86c6f5b93795ed5f638d699a827fd712e09fdbda34675c58bc8e500544954eb
Tx public key: 8caa7f4f4d3d1be7eaae4217b74efd48c4f38254ba7ce4c6e9d7271942381fd3
Timestamp: 1705370194 Timestamp [UCT]: 2024-01-16 01:56:34 Age [y:d:h:m:s]: 01:300:16:58:56
Block: 936237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473755 RingCT/type: yes/0
Extra: 018caa7f4f4d3d1be7eaae4217b74efd48c4f38254ba7ce4c6e9d7271942381fd30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9dfb40256c1344309a84a2461140e766337ba86471ffd2f6b8263b7544dc550 0.600000000000 1394261 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": 936247, "vin": [ { "gen": { "height": 936237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9dfb40256c1344309a84a2461140e766337ba86471ffd2f6b8263b7544dc550" } } ], "extra": [ 1, 140, 170, 127, 79, 77, 61, 27, 231, 234, 174, 66, 23, 183, 78, 253, 72, 196, 243, 130, 84, 186, 124, 228, 198, 233, 215, 39, 25, 66, 56, 31, 211, 2, 17, 0, 0, 0, 3, 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