Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f209a15e289300d2c050f48f7e6beb3b364c28cc9743e40df260c60e95af4269

Tx prefix hash: b594a2fc2cf117183471522dd6d6985f72a3387d6b6d4579091fce14c2d5f9e4
Tx public key: c93f3e6ef1ab0ee0396847b531a4072c3dde10a2f43246cbab7772df11032dec
Timestamp: 1722396181 Timestamp [UCT]: 2024-07-31 03:23:01 Age [y:d:h:m:s]: 00:232:09:48:03
Block: 1077414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166029 RingCT/type: yes/0
Extra: 01c93f3e6ef1ab0ee0396847b531a4072c3dde10a2f43246cbab7772df11032dec021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e182c1d50dec31092c1dbf3a68b70e08fc55a55c3f9090fdf2028288061ecb9f 0.600000000000 1549961 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": 1077424, "vin": [ { "gen": { "height": 1077414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e182c1d50dec31092c1dbf3a68b70e08fc55a55c3f9090fdf2028288061ecb9f" } } ], "extra": [ 1, 201, 63, 62, 110, 241, 171, 14, 224, 57, 104, 71, 181, 49, 164, 7, 44, 61, 222, 16, 162, 244, 50, 70, 203, 171, 119, 114, 223, 17, 3, 45, 236, 2, 17, 0, 0, 0, 7, 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