Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f12e03eeca40bf8b881d0e800bad5fb47d9b374ca39e33b45cdf58bc66ca61a

Tx prefix hash: 6584807a7eded432f81db544b44431a4b438f88d8de85f6ac0ecf266f2732a8b
Tx public key: bc864d2cf8e54222d68e755276e79bbfdd1d4f8f9f197d6e7f0dc79bab6d1e4b
Timestamp: 1709075846 Timestamp [UCT]: 2024-02-27 23:17:26 Age [y:d:h:m:s]: 01:062:09:13:17
Block: 966992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305628 RingCT/type: yes/0
Extra: 01bc864d2cf8e54222d68e755276e79bbfdd1d4f8f9f197d6e7f0dc79bab6d1e4b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1bf866280dfe1e7d73639217b83f0d1a1511cffe74ac1c04a5111af9310b71c 0.600000000000 1426763 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": 967002, "vin": [ { "gen": { "height": 966992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1bf866280dfe1e7d73639217b83f0d1a1511cffe74ac1c04a5111af9310b71c" } } ], "extra": [ 1, 188, 134, 77, 44, 248, 229, 66, 34, 214, 142, 117, 82, 118, 231, 155, 191, 221, 29, 79, 143, 159, 25, 125, 110, 127, 13, 199, 155, 171, 109, 30, 75, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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