Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426121fd5f818736ab4db40ca24889237dcd5b9b5b87e45025a9788c0d24bbf7

Tx prefix hash: cca22e3afdbebe43b8397dc9bdc07b1f642c0f03a46f5109547979312af1a17c
Tx public key: beb6f2cd8b2c9b2b067c09a67ffefd9003d54982f4bfc00652c43fdc24e5e25d
Timestamp: 1657160811 Timestamp [UCT]: 2022-07-07 02:26:51 Age [y:d:h:m:s]: 02:323:09:01:54
Block: 538290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 752294 RingCT/type: yes/0
Extra: 01beb6f2cd8b2c9b2b067c09a67ffefd9003d54982f4bfc00652c43fdc24e5e25d02110000001bd3fcec30000000000000000000

1 output(s) for total of 10.102338692000 dcy

stealth address amount amount idx
00: 77f05d2f47583e3f53e98d849532e906b41b87a9d84daf78cd392f4651c0b12b 10.102338692000 968271 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": 538300, "vin": [ { "gen": { "height": 538290 } } ], "vout": [ { "amount": 10102338692, "target": { "key": "77f05d2f47583e3f53e98d849532e906b41b87a9d84daf78cd392f4651c0b12b" } } ], "extra": [ 1, 190, 182, 242, 205, 139, 44, 155, 43, 6, 124, 9, 166, 127, 254, 253, 144, 3, 213, 73, 130, 244, 191, 192, 6, 82, 196, 63, 220, 36, 229, 226, 93, 2, 17, 0, 0, 0, 27, 211, 252, 236, 48, 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