Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5248cd305b383aaef58c214dea7a85f1546ccc47199088175bd856c84d08bc9

Tx prefix hash: 3902d805dbf0790213b033f424803b37571fa50b2c365d86e1d623f1ec3aafab
Tx public key: b32b9648caab630f6de1c28b9848e8c4de4acea797b8d58d05b6c65f8a2fe055
Timestamp: 1717663661 Timestamp [UCT]: 2024-06-06 08:47:41 Age [y:d:h:m:s]: 00:330:23:49:15
Block: 1038191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236567 RingCT/type: yes/0
Extra: 01b32b9648caab630f6de1c28b9848e8c4de4acea797b8d58d05b6c65f8a2fe05502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81b014002567b90caaa655fe95ef627aa3d4205d51dfaf7de590dbc33bf1efd9 0.600000000000 1506752 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": 1038201, "vin": [ { "gen": { "height": 1038191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81b014002567b90caaa655fe95ef627aa3d4205d51dfaf7de590dbc33bf1efd9" } } ], "extra": [ 1, 179, 43, 150, 72, 202, 171, 99, 15, 109, 225, 194, 139, 152, 72, 232, 196, 222, 74, 206, 167, 151, 184, 213, 141, 5, 182, 198, 95, 138, 47, 224, 85, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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