Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ac433fa682895e130eacd7163f15c2c300ae10c19b7368ddc953c3a26a67926

Tx prefix hash: ebf2670364bce3262500efd42fb7e316acad4a0397df34089dd33b4aa78bae33
Tx public key: 9a90813f139d07b45a7ca1c88576ff1dbd39a7b930c853f91b9a4c2465ecaf98
Timestamp: 1712016173 Timestamp [UCT]: 2024-04-02 00:02:53 Age [y:d:h:m:s]: 01:050:19:00:22
Block: 991326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297347 RingCT/type: yes/0
Extra: 019a90813f139d07b45a7ca1c88576ff1dbd39a7b930c853f91b9a4c2465ecaf980211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 178a1edce872f1814dbd934dce914980805e478c2b5c5391a12351ae19c7f919 0.600000000000 1451660 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": 991336, "vin": [ { "gen": { "height": 991326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "178a1edce872f1814dbd934dce914980805e478c2b5c5391a12351ae19c7f919" } } ], "extra": [ 1, 154, 144, 129, 63, 19, 157, 7, 180, 90, 124, 161, 200, 133, 118, 255, 29, 189, 57, 167, 185, 48, 200, 83, 249, 27, 154, 76, 36, 101, 236, 175, 152, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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