Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76c15b57737ef2a6fe30759be6b7627d651dc65bd115b4f70e63176adef75326

Tx prefix hash: 5494c967d3d5b67a3a2ab63c8d296d83c585476fee31c0cb6e27fb43ef951f3c
Tx public key: 0c83268b814b64bacaeccc3ca553c9f377374f0c3be8ca6c9def1d54523fe6ce
Timestamp: 1728598407 Timestamp [UCT]: 2024-10-10 22:13:27 Age [y:d:h:m:s]: 00:168:14:47:08
Block: 1128840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120294 RingCT/type: yes/0
Extra: 010c83268b814b64bacaeccc3ca553c9f377374f0c3be8ca6c9def1d54523fe6ce02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb431ccf7c2cb387fe95dd688eb3065dd7a393611f4aee33a4259107e02a2acf 0.600000000000 1611663 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": 1128850, "vin": [ { "gen": { "height": 1128840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb431ccf7c2cb387fe95dd688eb3065dd7a393611f4aee33a4259107e02a2acf" } } ], "extra": [ 1, 12, 131, 38, 139, 129, 75, 100, 186, 202, 236, 204, 60, 165, 83, 201, 243, 119, 55, 79, 12, 59, 232, 202, 108, 157, 239, 29, 84, 82, 63, 230, 206, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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