Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2ba2aed89d14703eb4920e40995c01a3cf5b13eec77fc2dfa3d6b41a4882633

Tx prefix hash: c3e3e729eb4e045d1fb6fd0f8265aff4f2581f0fbc4a3474ed6b366a4e62c7c0
Tx public key: 98154554351cb1d9e87807ee7a47bbb08fb6b96987e99b04103d6e801d2be5e3
Timestamp: 1666281595 Timestamp [UCT]: 2022-10-20 15:59:55 Age [y:d:h:m:s]: 03:015:11:44:39
Block: 613226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 791301 RingCT/type: yes/0
Extra: 0198154554351cb1d9e87807ee7a47bbb08fb6b96987e99b04103d6e801d2be5e302110000001475e3f0e9000000000000000000

1 output(s) for total of 5.703320009000 dcy

stealth address amount amount idx
00: 4d5a7836009ffc61ad2a410b9d825af547fff9943ad4418937e7b56e4d4fcb5f 5.703320009000 1050497 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": 613236, "vin": [ { "gen": { "height": 613226 } } ], "vout": [ { "amount": 5703320009, "target": { "key": "4d5a7836009ffc61ad2a410b9d825af547fff9943ad4418937e7b56e4d4fcb5f" } } ], "extra": [ 1, 152, 21, 69, 84, 53, 28, 177, 217, 232, 120, 7, 238, 122, 71, 187, 176, 143, 182, 185, 105, 135, 233, 155, 4, 16, 61, 110, 128, 29, 43, 229, 227, 2, 17, 0, 0, 0, 20, 117, 227, 240, 233, 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