Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8cd9a5ed1e0ba7fd45db834ba4c335b47f4cf6443c3ce17ee1ba70a91b40c11

Tx prefix hash: 2e52d24068263de63d719e50bf465250f2e960aff0ae2460f6ab2d1e39bb27d7
Tx public key: d834163b7d15c9603fbdbedd0d1350c4f42bedb8ee2b8acfec0f0e76d822ef44
Timestamp: 1704808407 Timestamp [UCT]: 2024-01-09 13:53:27 Age [y:d:h:m:s]: 01:069:01:52:42
Block: 931603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310477 RingCT/type: yes/0
Extra: 01d834163b7d15c9603fbdbedd0d1350c4f42bedb8ee2b8acfec0f0e76d822ef440211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6505625ff4ab04a23a3d62a77e452cf7a01148af5d39ab2c061c08b05bb880 0.600000000000 1389507 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": 931613, "vin": [ { "gen": { "height": 931603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6505625ff4ab04a23a3d62a77e452cf7a01148af5d39ab2c061c08b05bb880" } } ], "extra": [ 1, 216, 52, 22, 59, 125, 21, 201, 96, 63, 189, 190, 221, 13, 19, 80, 196, 244, 43, 237, 184, 238, 43, 138, 207, 236, 15, 14, 118, 216, 34, 239, 68, 2, 17, 0, 0, 0, 4, 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