Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee348521c4bf2cd34dfe51f2cae6b79c8ed9ba118cbe0952d53a7f5a5f82a671

Tx prefix hash: 6d0f71755178b704d7e9707097eb15ed325801ae88a47f0966e8ee9ed8d2536a
Tx public key: 25842e2067a849f9bb8b9d67d49883b25b3661349ae8ae82b34da1bb49696a80
Timestamp: 1721463369 Timestamp [UCT]: 2024-07-20 08:16:09 Age [y:d:h:m:s]: 00:246:09:20:08
Block: 1069682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176022 RingCT/type: yes/0
Extra: 0125842e2067a849f9bb8b9d67d49883b25b3661349ae8ae82b34da1bb49696a80021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c408755ca32c9b836a0c2c9e7413340a4e9a31913fb809a6e75c2fc236c274ab 0.600000000000 1541211 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": 1069692, "vin": [ { "gen": { "height": 1069682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c408755ca32c9b836a0c2c9e7413340a4e9a31913fb809a6e75c2fc236c274ab" } } ], "extra": [ 1, 37, 132, 46, 32, 103, 168, 73, 249, 187, 139, 157, 103, 212, 152, 131, 178, 91, 54, 97, 52, 154, 232, 174, 130, 179, 77, 161, 187, 73, 105, 106, 128, 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