Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c22ac0fce2e31f757bf568a4c83d596a3d4e32ba391168086660dc3630149d

Tx prefix hash: db90b697f9d28ce37b3b444c43a6c4f29e08ca78bac634a0a546e1a55cb57dae
Tx public key: ff2fa456ff6dcd0184a0ecd5f45de2fffc51b90f6d9002c6c4da9bcf1ca0b546
Timestamp: 1582244244 Timestamp [UCT]: 2020-02-21 00:17:24 Age [y:d:h:m:s]: 04:321:10:41:56
Block: 69013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122403 RingCT/type: yes/0
Extra: 01ff2fa456ff6dcd0184a0ecd5f45de2fffc51b90f6d9002c6c4da9bcf1ca0b546021100000025d81c26c0000000000000000000

1 output(s) for total of 362.520096951000 dcy

stealth address amount amount idx
00: 80a34e96d521e2981dce1e45def26e09eb88619789a5c7220bd8f387cdfadd44 362.520096951000 127312 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": 69023, "vin": [ { "gen": { "height": 69013 } } ], "vout": [ { "amount": 362520096951, "target": { "key": "80a34e96d521e2981dce1e45def26e09eb88619789a5c7220bd8f387cdfadd44" } } ], "extra": [ 1, 255, 47, 164, 86, 255, 109, 205, 1, 132, 160, 236, 213, 244, 93, 226, 255, 252, 81, 185, 15, 109, 144, 2, 198, 196, 218, 155, 207, 28, 160, 181, 70, 2, 17, 0, 0, 0, 37, 216, 28, 38, 192, 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