Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e809a654f170b59c2be515c92095d7448d28de5542ce1e99d8a72d76cad32d

Tx prefix hash: 4a2f7440724fd59cc31711f2c122ffe13e61c35f688b92bcf915a52fd36e831f
Tx public key: 281c6750bbe81582310b4560e880cd1acf878df4d52d91b8f0807feda04cc084
Timestamp: 1704460127 Timestamp [UCT]: 2024-01-05 13:08:47 Age [y:d:h:m:s]: 00:310:17:15:20
Block: 928702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222499 RingCT/type: yes/0
Extra: 01281c6750bbe81582310b4560e880cd1acf878df4d52d91b8f0807feda04cc08402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e97fce4c0894ac0b181cb4f1bfe1bef9a8b5037a21de050e4c92efaa0f95e1d0 0.600000000000 1386562 of 15

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": 928712, "vin": [ { "gen": { "height": 928702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e97fce4c0894ac0b181cb4f1bfe1bef9a8b5037a21de050e4c92efaa0f95e1d0" } } ], "extra": [ 1, 40, 28, 103, 80, 187, 232, 21, 130, 49, 11, 69, 96, 232, 128, 205, 26, 207, 135, 141, 244, 213, 45, 145, 184, 240, 128, 127, 237, 160, 76, 192, 132, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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