Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5966accd58f023820f513b3cdb4262dc2e237ec98d7033064ed596aebbc6b2f

Tx prefix hash: a39c64485711369c2f8e6073a201907a7d3928e92257a1ba037a46ba23e685b7
Tx public key: 44d087536dbe2b70cc23a51ae051b2377e8f605dc8e876e47cf8713aa1eea490
Timestamp: 1726306602 Timestamp [UCT]: 2024-09-14 09:36:42 Age [y:d:h:m:s]: 00:130:18:31:47
Block: 1109834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93482 RingCT/type: yes/0
Extra: 0144d087536dbe2b70cc23a51ae051b2377e8f605dc8e876e47cf8713aa1eea490021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eb1856efd122e4f87ab6f461d54e3b1726d7af9a89384347647770a2387f2f9 0.600000000000 1588229 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": 1109844, "vin": [ { "gen": { "height": 1109834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eb1856efd122e4f87ab6f461d54e3b1726d7af9a89384347647770a2387f2f9" } } ], "extra": [ 1, 68, 208, 135, 83, 109, 190, 43, 112, 204, 35, 165, 26, 224, 81, 178, 55, 126, 143, 96, 93, 200, 232, 118, 228, 124, 248, 113, 58, 161, 238, 164, 144, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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