Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e97989c0e08f06f78bc04fc4b45f71634e0bbe0f78bd2bbdd90905f3bddad4f6

Tx prefix hash: 49b235117393d1b36e8ec6d62a176f48a7e0eb05dd5f0bfaf91aaa3e3451ee2c
Tx public key: db6cb8f8fbceb7840ae6eed024e950788f9837b62436e820ffae54bea521b23c
Timestamp: 1674215637 Timestamp [UCT]: 2023-01-20 11:53:57 Age [y:d:h:m:s]: 02:000:23:19:57
Block: 678848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522529 RingCT/type: yes/0
Extra: 01db6cb8f8fbceb7840ae6eed024e950788f9837b62436e820ffae54bea521b23c0211000000035029cbac000000000000000000

1 output(s) for total of 3.456962887000 dcy

stealth address amount amount idx
00: a37fa24d2e67d5e9fce9bb18b9f290fd217a9ef09d2e4abbb70f386fa49ca9cd 3.456962887000 1120795 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": 678858, "vin": [ { "gen": { "height": 678848 } } ], "vout": [ { "amount": 3456962887, "target": { "key": "a37fa24d2e67d5e9fce9bb18b9f290fd217a9ef09d2e4abbb70f386fa49ca9cd" } } ], "extra": [ 1, 219, 108, 184, 248, 251, 206, 183, 132, 10, 230, 238, 208, 36, 233, 80, 120, 143, 152, 55, 182, 36, 54, 232, 32, 255, 174, 84, 190, 165, 33, 178, 60, 2, 17, 0, 0, 0, 3, 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