Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d104fbf0fa08fa9b9f579ce490f1ffbbcc99caf4b62a744d54f7d6087c1526f

Tx prefix hash: 6b1843d3803070ed431a3858012a65b17f18bca5404fad6ec052a0d9d8bd9595
Tx public key: ceb0a6eb2257ed0a5041eb33c4d712d47ec60c88af2c94e8c90e4173dce4fdd0
Timestamp: 1730528368 Timestamp [UCT]: 2024-11-02 06:19:28 Age [y:d:h:m:s]: 00:149:16:48:21
Block: 1144755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106822 RingCT/type: yes/0
Extra: 01ceb0a6eb2257ed0a5041eb33c4d712d47ec60c88af2c94e8c90e4173dce4fdd00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea9b446db657a60cc3d27072dee81fe120c66d53dd85e59ae2e375716a9d8df3 0.600000000000 1629054 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": 1144765, "vin": [ { "gen": { "height": 1144755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea9b446db657a60cc3d27072dee81fe120c66d53dd85e59ae2e375716a9d8df3" } } ], "extra": [ 1, 206, 176, 166, 235, 34, 87, 237, 10, 80, 65, 235, 51, 196, 215, 18, 212, 126, 198, 12, 136, 175, 44, 148, 232, 201, 14, 65, 115, 220, 228, 253, 208, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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