Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb8a1223d467b4a079537ec82d689617363bd8fdf436dc0f3915bf405c6c6bf2

Tx prefix hash: a36fd292d97d6ea5ec120cfe123ed0f113a8ae6f61ce74c0b739c73851101c67
Tx public key: b9b8e43084265fb77810a50fcd2174bcb51e391b78881d45ce85729fb420ba4f
Timestamp: 1710391237 Timestamp [UCT]: 2024-03-14 04:40:37 Age [y:d:h:m:s]: 01:251:10:57:11
Block: 977916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438402 RingCT/type: yes/0
Extra: 01b9b8e43084265fb77810a50fcd2174bcb51e391b78881d45ce85729fb420ba4f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dab383ecc9cfa49d8a44ed6e7ffdac7aac903f6fa21ef88e19c710e64f7c9675 0.600000000000 1437925 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": 977926, "vin": [ { "gen": { "height": 977916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dab383ecc9cfa49d8a44ed6e7ffdac7aac903f6fa21ef88e19c710e64f7c9675" } } ], "extra": [ 1, 185, 184, 228, 48, 132, 38, 95, 183, 120, 16, 165, 15, 205, 33, 116, 188, 181, 30, 57, 27, 120, 136, 29, 69, 206, 133, 114, 159, 180, 32, 186, 79, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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