Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a8bac50053604892b1d30076b2085b7cc8417e084d6c5b6a563832b5e48ef1

Tx prefix hash: df08fec6bb2983a739e02e839cf5bc8fcdca927365a7122e38279442110da79e
Tx public key: b0cb6ce7cf5be3aaf0aeacc3430d01a49adcfa77d9171893f58f54d72ac0f595
Timestamp: 1671891091 Timestamp [UCT]: 2022-12-24 14:11:31 Age [y:d:h:m:s]: 02:104:15:46:39
Block: 659591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 596471 RingCT/type: yes/0
Extra: 01b0cb6ce7cf5be3aaf0aeacc3430d01a49adcfa77d9171893f58f54d72ac0f59502110000000433af99f4000000000000000000

1 output(s) for total of 4.004065565000 dcy

stealth address amount amount idx
00: fb3432f963a18a6436730dfe50ae8b1aeafc4571319543780bbf93bda54ca8e8 4.004065565000 1100298 of 0

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": 659601, "vin": [ { "gen": { "height": 659591 } } ], "vout": [ { "amount": 4004065565, "target": { "key": "fb3432f963a18a6436730dfe50ae8b1aeafc4571319543780bbf93bda54ca8e8" } } ], "extra": [ 1, 176, 203, 108, 231, 207, 91, 227, 170, 240, 174, 172, 195, 67, 13, 1, 164, 154, 220, 250, 119, 217, 23, 24, 147, 245, 143, 84, 215, 42, 192, 245, 149, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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