Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fbca0ccc181cd9b3ec8f4dd9d8254a8d99d14e24a13867f663525be7ac6be8

Tx prefix hash: 94287109d3d82f2a4d51163a15f4a679d5c1752cbabfb1ec84de044b3c757136
Tx public key: 1d7d07430ec9a69851bf9f48655417734c7b9a68fb22f27039c9302c9aa696a2
Timestamp: 1733799308 Timestamp [UCT]: 2024-12-10 02:55:08 Age [y:d:h:m:s]: 00:190:20:53:31
Block: 1171867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136109 RingCT/type: yes/0
Extra: 011d7d07430ec9a69851bf9f48655417734c7b9a68fb22f27039c9302c9aa696a2021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cfa0d666cf35c93086a6c44246da668284b8903c1214d9be21421bcefb5c60f 0.600000000000 1657684 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": 1171877, "vin": [ { "gen": { "height": 1171867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cfa0d666cf35c93086a6c44246da668284b8903c1214d9be21421bcefb5c60f" } } ], "extra": [ 1, 29, 125, 7, 67, 14, 201, 166, 152, 81, 191, 159, 72, 101, 84, 23, 115, 76, 123, 154, 104, 251, 34, 242, 112, 57, 201, 48, 44, 154, 166, 150, 162, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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