Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba44d05eae07d8a7193453e7a14a8a27db1fffc014d857f5e74ae7fce4eb8151

Tx prefix hash: f703b344ab23b467d4ec333976280e4121e8baf8375be1c7e4c0245f14257056
Tx public key: a2f75d1cb23cab3e74283ff5e65ba6b9934dfba9ba36b380404677ad630b0e5e
Timestamp: 1703743084 Timestamp [UCT]: 2023-12-28 05:58:04 Age [y:d:h:m:s]: 01:177:03:46:35
Block: 922777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387590 RingCT/type: yes/0
Extra: 01a2f75d1cb23cab3e74283ff5e65ba6b9934dfba9ba36b380404677ad630b0e5e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04d7dec32bef4397db3e825a00c7429899f113fe9ccc27ee4ebb8aa22de5eed5 0.600000000000 1380481 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": 922787, "vin": [ { "gen": { "height": 922777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04d7dec32bef4397db3e825a00c7429899f113fe9ccc27ee4ebb8aa22de5eed5" } } ], "extra": [ 1, 162, 247, 93, 28, 178, 60, 171, 62, 116, 40, 63, 245, 230, 91, 166, 185, 147, 77, 251, 169, 186, 54, 179, 128, 64, 70, 119, 173, 99, 11, 14, 94, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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