Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f30bf09ed1725e9f14d0f39e70352c5bf444f4a82af67886c7ca6fd09326a2

Tx prefix hash: 59c62f32d3ab76a86443ea3afe7acadb92d4bf9027075f95aec850cd7794b24d
Tx public key: b1c9fff434ab3becfa87cdcaf8a81562017d0f6bf7d247aa889fcc7be7319695
Timestamp: 1721607018 Timestamp [UCT]: 2024-07-22 00:10:18 Age [y:d:h:m:s]: 00:171:11:40:03
Block: 1070862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122715 RingCT/type: yes/0
Extra: 01b1c9fff434ab3becfa87cdcaf8a81562017d0f6bf7d247aa889fcc7be7319695021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7952cc33dfd14fdd5e4b935a73c6ed0b7eafe4448a631e29160b2da619b37b8a 0.600000000000 1542873 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": 1070872, "vin": [ { "gen": { "height": 1070862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7952cc33dfd14fdd5e4b935a73c6ed0b7eafe4448a631e29160b2da619b37b8a" } } ], "extra": [ 1, 177, 201, 255, 244, 52, 171, 59, 236, 250, 135, 205, 202, 248, 168, 21, 98, 1, 125, 15, 107, 247, 210, 71, 170, 136, 159, 204, 123, 231, 49, 150, 149, 2, 17, 0, 0, 0, 3, 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