Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf4e4026bfc94ac4f3883a74ebf238d78f1d7e03c0dfa281adbbe02aeb8acdc

Tx prefix hash: 86423287b6c71ba2aeeea8754eb7452de977da35be2adcb1b4000c1e78aaa075
Tx public key: ae42ca4e0e2e521880360dd146d75ca780ef223af3d415608dfe2338764d55ec
Timestamp: 1656987730 Timestamp [UCT]: 2022-07-05 02:22:10 Age [y:d:h:m:s]: 02:259:19:28:20
Block: 536848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706843 RingCT/type: yes/0
Extra: 01ae42ca4e0e2e521880360dd146d75ca780ef223af3d415608dfe2338764d55ec021100000001e6d27f9c000000000000000000

1 output(s) for total of 10.214094494000 dcy

stealth address amount amount idx
00: c85568f78c6ab0f0b825ab2a8352b25b2cb5acc2262ccba1e448815be0493a2f 10.214094494000 966655 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": 536858, "vin": [ { "gen": { "height": 536848 } } ], "vout": [ { "amount": 10214094494, "target": { "key": "c85568f78c6ab0f0b825ab2a8352b25b2cb5acc2262ccba1e448815be0493a2f" } } ], "extra": [ 1, 174, 66, 202, 78, 14, 46, 82, 24, 128, 54, 13, 209, 70, 215, 92, 167, 128, 239, 34, 58, 243, 212, 21, 96, 141, 254, 35, 56, 118, 77, 85, 236, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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