Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b726a54d3a09e5d89943d94c678062ff1d78e624f18966bcb23370593c63aa9c

Tx prefix hash: cfa9565a616bfb3112dd4e14bc0a8bd43ddd8a4d7f4d188a2c8db5eec39a8384
Tx public key: f21c4ff137e86cc1fcc1a3532f6ca7d738eb9e1431a6cc24295361410e4a2af2
Timestamp: 1732238023 Timestamp [UCT]: 2024-11-22 01:13:43 Age [y:d:h:m:s]: 00:002:05:15:00
Block: 1158924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1575 RingCT/type: yes/0
Extra: 01f21c4ff137e86cc1fcc1a3532f6ca7d738eb9e1431a6cc24295361410e4a2af20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aaf9e79404efb46fce659ca3fa578b8b1a21b39b97b183409e5e982601387d7 0.600000000000 1644555 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": 1158934, "vin": [ { "gen": { "height": 1158924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aaf9e79404efb46fce659ca3fa578b8b1a21b39b97b183409e5e982601387d7" } } ], "extra": [ 1, 242, 28, 79, 241, 55, 232, 108, 193, 252, 193, 163, 83, 47, 108, 167, 215, 56, 235, 158, 20, 49, 166, 204, 36, 41, 83, 97, 65, 14, 74, 42, 242, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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