Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d51e9d14c432d103422618b4b45e0302feda104a453d5ada38dfb0bb1140f6b

Tx prefix hash: 1bbc671f89182b780119a3bd38ff69c47d6fc6fd6a0f14d1ea62d04655a44658
Tx public key: bb82276cf505649bdbc823142fafbf7dfe53f60b5a90459947e206c327d8f984
Timestamp: 1731747943 Timestamp [UCT]: 2024-11-16 09:05:43 Age [y:d:h:m:s]: 00:129:00:40:29
Block: 1154863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92025 RingCT/type: yes/0
Extra: 01bb82276cf505649bdbc823142fafbf7dfe53f60b5a90459947e206c327d8f984021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 825f29cd8e6f9e426700c0ff1ad91c0d22fd30544a8af3d703f7971ff7d12209 0.600000000000 1640476 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": 1154873, "vin": [ { "gen": { "height": 1154863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "825f29cd8e6f9e426700c0ff1ad91c0d22fd30544a8af3d703f7971ff7d12209" } } ], "extra": [ 1, 187, 130, 39, 108, 245, 5, 100, 155, 219, 200, 35, 20, 47, 175, 191, 125, 254, 83, 246, 11, 90, 144, 69, 153, 71, 226, 6, 195, 39, 216, 249, 132, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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