Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971f46aa1d4e96e79e5ce200189c12cfac7e0b716e98398e382736adb7c8e640

Tx prefix hash: 5890ac35ab41dd5c8cc6edc4e07fca4d005b570eb6930d9eb4e5d70237216948
Tx public key: 9982986f30118238e1d15233e07e6a3bab9f3d8f15f4cf10ffc89201fd3ecf2a
Timestamp: 1722022168 Timestamp [UCT]: 2024-07-26 19:29:28 Age [y:d:h:m:s]: 00:276:12:39:05
Block: 1074321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197571 RingCT/type: yes/0
Extra: 019982986f30118238e1d15233e07e6a3bab9f3d8f15f4cf10ffc89201fd3ecf2a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ebf6aab1ecd5e670a0754339947176ca32f0ee37e28339b8a8b4f2b9d4c7c10 0.600000000000 1546834 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": 1074331, "vin": [ { "gen": { "height": 1074321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ebf6aab1ecd5e670a0754339947176ca32f0ee37e28339b8a8b4f2b9d4c7c10" } } ], "extra": [ 1, 153, 130, 152, 111, 48, 17, 130, 56, 225, 209, 82, 51, 224, 126, 106, 59, 171, 159, 61, 143, 21, 244, 207, 16, 255, 200, 146, 1, 253, 62, 207, 42, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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