Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28a8f522a424ee8f9aba72194ff3356074df7dce5b9da637c090f7460487463

Tx prefix hash: deb3f5fd6f33a135b04ef7573db1d730d894a17594c7c68fc3774ec5df58529c
Tx public key: 9f5d34defac28d2f4bf177e849f891b4b993ad4b8f4945b54e519568bcb4ec85
Timestamp: 1708141485 Timestamp [UCT]: 2024-02-17 03:44:45 Age [y:d:h:m:s]: 01:119:19:01:17
Block: 959233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346600 RingCT/type: yes/0
Extra: 019f5d34defac28d2f4bf177e849f891b4b993ad4b8f4945b54e519568bcb4ec850211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68fc1489d9c983d5927636775a1af5154bfb35f6fcfd4ab1800a4ccaec63563d 0.600000000000 1418764 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": 959243, "vin": [ { "gen": { "height": 959233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68fc1489d9c983d5927636775a1af5154bfb35f6fcfd4ab1800a4ccaec63563d" } } ], "extra": [ 1, 159, 93, 52, 222, 250, 194, 141, 47, 75, 241, 119, 232, 73, 248, 145, 180, 185, 147, 173, 75, 143, 73, 69, 181, 78, 81, 149, 104, 188, 180, 236, 133, 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