Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a904baf6b8fb775a817deea5b96d09131bf08901b5f555bfa4f260d3d14144cc

Tx prefix hash: 3e8e87b96c3fe24b829d52a59157f86a7de3cdf88fd20583aefdd5b1b47273d9
Tx public key: b5bf37110342b396bb86df79b37a4337d0b82cb03cc97b33cf92eb80cf210b9d
Timestamp: 1707032653 Timestamp [UCT]: 2024-02-04 07:44:13 Age [y:d:h:m:s]: 01:075:19:50:38
Block: 950037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315271 RingCT/type: yes/0
Extra: 01b5bf37110342b396bb86df79b37a4337d0b82cb03cc97b33cf92eb80cf210b9d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d103315e191691ea5c32280d0e051a4a1f23d66f140090e08ec2778d9273654d 0.600000000000 1408589 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": 950047, "vin": [ { "gen": { "height": 950037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d103315e191691ea5c32280d0e051a4a1f23d66f140090e08ec2778d9273654d" } } ], "extra": [ 1, 181, 191, 55, 17, 3, 66, 179, 150, 187, 134, 223, 121, 179, 122, 67, 55, 208, 184, 44, 176, 60, 201, 123, 51, 207, 146, 235, 128, 207, 33, 11, 157, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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