Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb18087854d7f3735c04584da32ceb6873f0f05c42cf723286c1df3f02aeb704

Tx prefix hash: 026009838203b1ef946b2948894ab735c4b25307457a2bd2a2ec47db620974a6
Tx public key: f7e680a7b61d6c5e5be698d65ef3eebf7230e3970860bfe95fcf590a7f5ee0ea
Timestamp: 1681376816 Timestamp [UCT]: 2023-04-13 09:06:56 Age [y:d:h:m:s]: 02:034:02:09:03
Block: 737576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546545 RingCT/type: yes/0
Extra: 01f7e680a7b61d6c5e5be698d65ef3eebf7230e3970860bfe95fcf590a7f5ee0ea0211000000015029cbac000000000000000000

1 output(s) for total of 2.208537364000 dcy

stealth address amount amount idx
00: 2acf4a59f4cdd3017142d253cf64d45fb95b49bfc679c49caf8e2a81a776a457 2.208537364000 1184155 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": 737586, "vin": [ { "gen": { "height": 737576 } } ], "vout": [ { "amount": 2208537364, "target": { "key": "2acf4a59f4cdd3017142d253cf64d45fb95b49bfc679c49caf8e2a81a776a457" } } ], "extra": [ 1, 247, 230, 128, 167, 182, 29, 108, 94, 91, 230, 152, 214, 94, 243, 238, 191, 114, 48, 227, 151, 8, 96, 191, 233, 95, 207, 89, 10, 127, 94, 224, 234, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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