Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0c2bb3551bbb36786a76b4357856773d217d9d7e5747c1ff8386c06cb7878f

Tx prefix hash: e3df744da179c6ee13e418ddfc6425aaee7c3f30483a7f8a32bf77909493b207
Tx public key: 9ff8ee77b5142d976f929303658bbefbbfe62ddbad2e1c3645e83bba4e1cfb29
Timestamp: 1656935151 Timestamp [UCT]: 2022-07-04 11:45:51 Age [y:d:h:m:s]: 02:317:00:34:41
Block: 536433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 747728 RingCT/type: yes/0
Extra: 019ff8ee77b5142d976f929303658bbefbbfe62ddbad2e1c3645e83bba4e1cfb290211000000122e6b1fd5000000000000000000

1 output(s) for total of 10.246485722000 dcy

stealth address amount amount idx
00: b74b5d517439d115e6594153aa078b2232c97b019d2cf6c0a95844eec9f3b162 10.246485722000 966194 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": 536443, "vin": [ { "gen": { "height": 536433 } } ], "vout": [ { "amount": 10246485722, "target": { "key": "b74b5d517439d115e6594153aa078b2232c97b019d2cf6c0a95844eec9f3b162" } } ], "extra": [ 1, 159, 248, 238, 119, 181, 20, 45, 151, 111, 146, 147, 3, 101, 139, 190, 251, 191, 230, 45, 219, 173, 46, 28, 54, 69, 232, 59, 186, 78, 28, 251, 41, 2, 17, 0, 0, 0, 18, 46, 107, 31, 213, 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