Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39dec236da3b0f2a0aab1d1d741ddd43100558af9302e07fc0fbf3faf4a16b0

Tx prefix hash: ae111085dd1fcc9666c3f271cf15a922a76c8a8046ef7f574ca84f57911f6a81
Tx public key: bb868fcdc6696686093a09a33d947e57ae05d0951edbe3bdb2388a881b39eb27
Timestamp: 1712269562 Timestamp [UCT]: 2024-04-04 22:26:02 Age [y:d:h:m:s]: 00:224:01:28:52
Block: 993448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160426 RingCT/type: yes/0
Extra: 01bb868fcdc6696686093a09a33d947e57ae05d0951edbe3bdb2388a881b39eb270211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2695e3d9e8e3e28daccd48046466743404d9bdb07303e907a3545dbf4a6ead3d 0.600000000000 1453834 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": 993458, "vin": [ { "gen": { "height": 993448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2695e3d9e8e3e28daccd48046466743404d9bdb07303e907a3545dbf4a6ead3d" } } ], "extra": [ 1, 187, 134, 143, 205, 198, 105, 102, 134, 9, 58, 9, 163, 61, 148, 126, 87, 174, 5, 208, 149, 30, 219, 227, 189, 178, 56, 138, 136, 27, 57, 235, 39, 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