Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0834340ccce57b40fd66058f6670453d2c6b21950155ad1011a667f46de162b1

Tx prefix hash: 1aa9dc50d90ae0cc55a5ef3faa7d4139329b15a11f9aaf7ee0ef2f6d7d8d95b9
Tx public key: 3c204c186abe95be10117b3f53add929df4356ba20eb0b119c838a3cac029fe5
Timestamp: 1669326592 Timestamp [UCT]: 2022-11-24 21:49:52 Age [y:d:h:m:s]: 02:116:01:37:18
Block: 638351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604686 RingCT/type: yes/0
Extra: 013c204c186abe95be10117b3f53add929df4356ba20eb0b119c838a3cac029fe5021100000001e7ace25d000000000000000000

1 output(s) for total of 4.708452012000 dcy

stealth address amount amount idx
00: da24e2a8171cc05565eba69d3ae9a459294bce7481b1d3cabddc39ae1c38c8b3 4.708452012000 1077954 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": 638361, "vin": [ { "gen": { "height": 638351 } } ], "vout": [ { "amount": 4708452012, "target": { "key": "da24e2a8171cc05565eba69d3ae9a459294bce7481b1d3cabddc39ae1c38c8b3" } } ], "extra": [ 1, 60, 32, 76, 24, 106, 190, 149, 190, 16, 17, 123, 63, 83, 173, 217, 41, 223, 67, 86, 186, 32, 235, 11, 17, 156, 131, 138, 60, 172, 2, 159, 229, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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