Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d304b9ecde302af4f31167f2c0ef0eba7fbc628fc11b6633f4ca1b4e61838f7

Tx prefix hash: 5d5e20e8e62e19a930fe6b09525899338f1d94c2d68378701c06c5f8dde6388f
Tx public key: a6d730a292d271b35d553301c796cbce4f32474913a9004148c31c0f970ddbc5
Timestamp: 1712473281 Timestamp [UCT]: 2024-04-07 07:01:21 Age [y:d:h:m:s]: 01:213:18:14:45
Block: 995122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411466 RingCT/type: yes/0
Extra: 01a6d730a292d271b35d553301c796cbce4f32474913a9004148c31c0f970ddbc502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c19e0f103f37c0998bbaee61b15f93a2ec161170172fe950dee74a1d770506a 0.600000000000 1455526 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": 995132, "vin": [ { "gen": { "height": 995122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c19e0f103f37c0998bbaee61b15f93a2ec161170172fe950dee74a1d770506a" } } ], "extra": [ 1, 166, 215, 48, 162, 146, 210, 113, 179, 93, 85, 51, 1, 199, 150, 203, 206, 79, 50, 71, 73, 19, 169, 0, 65, 72, 195, 28, 15, 151, 13, 219, 197, 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