Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15ee3d3b50debdba76fe11c0cca9f13b691a74e13c4e58eb4e399dd28bb295fe

Tx prefix hash: 9faf57f1aa829b23f89a95ea8851d5cf4bd5b5d9abd9254d5dbfeeb67142849d
Tx public key: 472b630a19050d13884f6f3593e47202674e0699a9c6bd370574943a0e3bfdb9
Timestamp: 1720751814 Timestamp [UCT]: 2024-07-12 02:36:54 Age [y:d:h:m:s]: 01:130:19:38:38
Block: 1063797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352015 RingCT/type: yes/0
Extra: 01472b630a19050d13884f6f3593e47202674e0699a9c6bd370574943a0e3bfdb902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35edf3b1438d7f2a448a9d8b57d817e2b296afa1609202b5e71c670f8eae6960 0.600000000000 1534314 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": 1063807, "vin": [ { "gen": { "height": 1063797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35edf3b1438d7f2a448a9d8b57d817e2b296afa1609202b5e71c670f8eae6960" } } ], "extra": [ 1, 71, 43, 99, 10, 25, 5, 13, 19, 136, 79, 111, 53, 147, 228, 114, 2, 103, 78, 6, 153, 169, 198, 189, 55, 5, 116, 148, 58, 14, 59, 253, 185, 2, 17, 0, 0, 0, 3, 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