Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a0bda48431d51058de40e67cc623b7ccea11ae709f70c68dfff41ab1c6e2ce

Tx prefix hash: db4986eaa74311d9724aa0bead079b9e9fd38bab44b55dea5acfe08d09de1228
Tx public key: 7af770b6f570e21c4cceb54e83a98a6fe84b756b26836191fa23afc50e544c7b
Timestamp: 1734046791 Timestamp [UCT]: 2024-12-12 23:39:51 Age [y:d:h:m:s]: 00:112:00:23:58
Block: 1173922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79837 RingCT/type: yes/0
Extra: 017af770b6f570e21c4cceb54e83a98a6fe84b756b26836191fa23afc50e544c7b021100000003a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74e0267aee557cc452e60f39493fdf0c6b7b0fb2ca17be5238909eb1b404891a 0.600000000000 1660011 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": 1173932, "vin": [ { "gen": { "height": 1173922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74e0267aee557cc452e60f39493fdf0c6b7b0fb2ca17be5238909eb1b404891a" } } ], "extra": [ 1, 122, 247, 112, 182, 245, 112, 226, 28, 76, 206, 181, 78, 131, 169, 138, 111, 232, 75, 117, 107, 38, 131, 97, 145, 250, 35, 175, 197, 14, 84, 76, 123, 2, 17, 0, 0, 0, 3, 162, 215, 95, 68, 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