Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba6f731ee9d75be7e0f1f476492056dddd0f755157a3a86a906658899ced19d0

Tx prefix hash: 385d6b1981316b42fb1df6c63ab21eb88fd4469f61b2a73c9556dfd756459a0c
Tx public key: 04d9d96f10f87a17ef302ac89be0f9574e44dc3a0d6837cbeb3ae8811af990f5
Timestamp: 1716012338 Timestamp [UCT]: 2024-05-18 06:05:38 Age [y:d:h:m:s]: 00:284:09:02:54
Block: 1024492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203236 RingCT/type: yes/0
Extra: 0104d9d96f10f87a17ef302ac89be0f9574e44dc3a0d6837cbeb3ae8811af990f50211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a62b22dad5cab015c8bcb8f595ef88fe97d85390f120fc1863441b5221ae75b6 0.600000000000 1490285 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": 1024502, "vin": [ { "gen": { "height": 1024492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a62b22dad5cab015c8bcb8f595ef88fe97d85390f120fc1863441b5221ae75b6" } } ], "extra": [ 1, 4, 217, 217, 111, 16, 248, 122, 23, 239, 48, 42, 200, 155, 224, 249, 87, 78, 68, 220, 58, 13, 104, 55, 203, 235, 58, 232, 129, 26, 249, 144, 245, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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