Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ff26e8b3fc3c2a2344f429f61e008eaf106e95085819b60e4833c53e00b3b6

Tx prefix hash: 7eef4c411f367e0be06c1fff1c352c2e46f0ecfa82301d4a7d12fdf6a45c4f73
Tx public key: bf65a1299851a40504418f91fc6187e6666c06483d6034e7aaba13f8b225f2df
Timestamp: 1714191016 Timestamp [UCT]: 2024-04-27 04:10:16 Age [y:d:h:m:s]: 00:147:18:51:37
Block: 1009384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105872 RingCT/type: yes/0
Extra: 01bf65a1299851a40504418f91fc6187e6666c06483d6034e7aaba13f8b225f2df02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 539049ea6e8272efa34624ad082a1c78dad7ba72938ee874a6043111900b95a2 0.600000000000 1471042 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": 1009394, "vin": [ { "gen": { "height": 1009384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "539049ea6e8272efa34624ad082a1c78dad7ba72938ee874a6043111900b95a2" } } ], "extra": [ 1, 191, 101, 161, 41, 152, 81, 164, 5, 4, 65, 143, 145, 252, 97, 135, 230, 102, 108, 6, 72, 61, 96, 52, 231, 170, 186, 19, 248, 178, 37, 242, 223, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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