Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba8b4064910a5f6981d3368a9ab632effd70df2cc8a104e2a185a9c4dd40ce8a

Tx prefix hash: 032d9515a889d8631755d4524eab0c350693eee0fc3fb71baa9bcd0a98f0f5c5
Tx public key: a1a84c60e9ef50f9f8ba68270454e767996e6a7ededaddefd89cbbe096a36778
Timestamp: 1672880004 Timestamp [UCT]: 2023-01-05 00:53:24 Age [y:d:h:m:s]: 02:116:18:00:02
Block: 667765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605139 RingCT/type: yes/0
Extra: 01a1a84c60e9ef50f9f8ba68270454e767996e6a7ededaddefd89cbbe096a3677802110000000152542ceb000000000000000000

1 output(s) for total of 3.761987196000 dcy

stealth address amount amount idx
00: 3c79aa9e115f8c5fe4d86dbfffc21b8b8be3092493d11f7d90dce5cef15d047a 3.761987196000 1108984 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": 667775, "vin": [ { "gen": { "height": 667765 } } ], "vout": [ { "amount": 3761987196, "target": { "key": "3c79aa9e115f8c5fe4d86dbfffc21b8b8be3092493d11f7d90dce5cef15d047a" } } ], "extra": [ 1, 161, 168, 76, 96, 233, 239, 80, 249, 248, 186, 104, 39, 4, 84, 231, 103, 153, 110, 106, 126, 222, 218, 221, 239, 216, 156, 187, 224, 150, 163, 103, 120, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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