Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a2a64ddd2b79275088fb342ac10984aa89d108e40150d6ed8d7f62c94f50dd

Tx prefix hash: cb741641793181c36cd733ae0ada576717d019bbf52edc080f7cf07ae4292672
Tx public key: 784b7baf48ea17fad4c3939f679d3396b6f68d20e004aa424f6fc10567e53f7d
Timestamp: 1706118970 Timestamp [UCT]: 2024-01-24 17:56:10 Age [y:d:h:m:s]: 01:287:07:55:57
Block: 942445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464161 RingCT/type: yes/0
Extra: 01784b7baf48ea17fad4c3939f679d3396b6f68d20e004aa424f6fc10567e53f7d0211000000038cc46cda000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d628f9dcbdab7cab23af1a3e326f0db8f0625d356b12900b6bbd6179690c29c9 0.600000000000 1400617 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": 942455, "vin": [ { "gen": { "height": 942445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d628f9dcbdab7cab23af1a3e326f0db8f0625d356b12900b6bbd6179690c29c9" } } ], "extra": [ 1, 120, 75, 123, 175, 72, 234, 23, 250, 212, 195, 147, 159, 103, 157, 51, 150, 182, 246, 141, 32, 224, 4, 170, 66, 79, 111, 193, 5, 103, 229, 63, 125, 2, 17, 0, 0, 0, 3, 140, 196, 108, 218, 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