Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bfdcfd318fae6fba4d954f5e3f4e342aa728462248bfcfc4b288cdb1cdd790f

Tx prefix hash: 9e3153e4779b5f5fdaa44ed2eb233506cf60ff1806189901a03e5cb608edaceb
Tx public key: 036bcf98d614130c379a2c3e88173bf9cc0d6e128b4c8fc84c394e242837026f
Timestamp: 1720190303 Timestamp [UCT]: 2024-07-05 14:38:23 Age [y:d:h:m:s]: 00:276:17:04:15
Block: 1059132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197701 RingCT/type: yes/0
Extra: 01036bcf98d614130c379a2c3e88173bf9cc0d6e128b4c8fc84c394e242837026f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd153e7d0d914255fe501911368a3dac4d779e38833f0999a08db7f8c2b8e8b 0.600000000000 1529593 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": 1059142, "vin": [ { "gen": { "height": 1059132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd153e7d0d914255fe501911368a3dac4d779e38833f0999a08db7f8c2b8e8b" } } ], "extra": [ 1, 3, 107, 207, 152, 214, 20, 19, 12, 55, 154, 44, 62, 136, 23, 59, 249, 204, 13, 110, 18, 139, 76, 143, 200, 76, 57, 78, 36, 40, 55, 2, 111, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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