Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e135ee47e8a5df7de20e9b5b501c4a9fa85ed43168f8fec2a04d91c97e39d97

Tx prefix hash: efc6aa0cf897ef43bdaef6de87e0ed8642da278c1ccd11e6ce400f1523e25de6
Tx public key: 6b89c8bcb3f7e0cdf0b9ab53d5113354886e6391c0e501e8e76acfe8e61afb93
Timestamp: 1721054198 Timestamp [UCT]: 2024-07-15 14:36:38 Age [y:d:h:m:s]: 00:100:08:44:18
Block: 1066309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71846 RingCT/type: yes/0
Extra: 016b89c8bcb3f7e0cdf0b9ab53d5113354886e6391c0e501e8e76acfe8e61afb9302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f8f80539211d0ec457fc89a97dc3d1f29dc28da1ff8346acfb6f17933b62f76 0.600000000000 1536882 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": 1066319, "vin": [ { "gen": { "height": 1066309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f8f80539211d0ec457fc89a97dc3d1f29dc28da1ff8346acfb6f17933b62f76" } } ], "extra": [ 1, 107, 137, 200, 188, 179, 247, 224, 205, 240, 185, 171, 83, 213, 17, 51, 84, 136, 110, 99, 145, 192, 229, 1, 232, 231, 106, 207, 232, 230, 26, 251, 147, 2, 17, 0, 0, 0, 9, 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