Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3a9c661ae72da41d1b74210c478ab5443739c727b30c7225a862e0c1bae810

Tx prefix hash: 0efade4fda5c863fef64cad07e6cbe75e8e728d6c28206dd0357d53dc5af35bd
Tx public key: 5b2658f6328a1b68d569c80cf592b9f54726aa4ce0e1eca92f2c0c1b698eca11
Timestamp: 1726545623 Timestamp [UCT]: 2024-09-17 04:00:23 Age [y:d:h:m:s]: 00:072:06:18:41
Block: 1111818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51667 RingCT/type: yes/0
Extra: 015b2658f6328a1b68d569c80cf592b9f54726aa4ce0e1eca92f2c0c1b698eca1102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94bd74d0afcf522e1d7f488a553683a20e9ebee439ae16c1889a97a551ce6b88 0.600000000000 1590913 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": 1111828, "vin": [ { "gen": { "height": 1111818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94bd74d0afcf522e1d7f488a553683a20e9ebee439ae16c1889a97a551ce6b88" } } ], "extra": [ 1, 91, 38, 88, 246, 50, 138, 27, 104, 213, 105, 200, 12, 245, 146, 185, 245, 71, 38, 170, 76, 224, 225, 236, 169, 47, 44, 12, 27, 105, 142, 202, 17, 2, 17, 0, 0, 0, 2, 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