Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02c441ffe46647e242d0babe3b35664d147649c1f4a2ba874c8ab45f71218b23

Tx prefix hash: 82ae801e0a810421df37995ba04859a5d25e913ef61cc6e84715909cf65ab629
Tx public key: c0b6ca6efe5f6664333d96d4023938981ab5b7c20e51897fe6bf0ab5411d05a7
Timestamp: 1659247823 Timestamp [UCT]: 2022-07-31 06:10:23 Age [y:d:h:m:s]: 02:326:12:05:58
Block: 555485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754440 RingCT/type: yes/0
Extra: 01c0b6ca6efe5f6664333d96d4023938981ab5b7c20e51897fe6bf0ab5411d05a7021100000001eae24e24000000000000000000

1 output(s) for total of 8.860285710000 dcy

stealth address amount amount idx
00: b9fb160a56da91cf6f340d7bcf0f2e24477fd64741e225149d29183fe0c496b7 8.860285710000 987389 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": 555495, "vin": [ { "gen": { "height": 555485 } } ], "vout": [ { "amount": 8860285710, "target": { "key": "b9fb160a56da91cf6f340d7bcf0f2e24477fd64741e225149d29183fe0c496b7" } } ], "extra": [ 1, 192, 182, 202, 110, 254, 95, 102, 100, 51, 61, 150, 212, 2, 57, 56, 152, 26, 181, 183, 194, 14, 81, 137, 127, 230, 191, 10, 181, 65, 29, 5, 167, 2, 17, 0, 0, 0, 1, 234, 226, 78, 36, 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