Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e92271f6d83bb4fcca7d46e1e26454a3fe0a08527813e01da921396037bb681

Tx prefix hash: 1e21b8da093b3cda3c2675254eaee9f9d832fc74073316b08ecec86a43f5af99
Tx public key: 3e1b42f13bf2c1b6cacd2d761b0c78d1d04ef5f6e9b746f4d1904a0f92437c87
Timestamp: 1713866351 Timestamp [UCT]: 2024-04-23 09:59:11 Age [y:d:h:m:s]: 00:253:02:28:54
Block: 1006708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181164 RingCT/type: yes/0
Extra: 013e1b42f13bf2c1b6cacd2d761b0c78d1d04ef5f6e9b746f4d1904a0f92437c870211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f936539dd88ed6cb66faa4d81baabca3daa2390de894dd6c513139675aa41ecf 0.600000000000 1467822 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": 1006718, "vin": [ { "gen": { "height": 1006708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f936539dd88ed6cb66faa4d81baabca3daa2390de894dd6c513139675aa41ecf" } } ], "extra": [ 1, 62, 27, 66, 241, 59, 242, 193, 182, 202, 205, 45, 118, 27, 12, 120, 209, 208, 78, 245, 246, 233, 183, 70, 244, 209, 144, 74, 15, 146, 67, 124, 135, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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