Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d07df5824cf507ab7b34244d4c83a7b6fb257a1f89fc6b649b0388c4d71d00

Tx prefix hash: 801088930c9b2a76cf8a0ad2eedf492fd4b1fa0c0a941ed0a6a2e6047eca24b0
Tx public key: 08470d2c98b5be6770a4841f6231b339805b79f9158745c136537da5a0c77665
Timestamp: 1716715618 Timestamp [UCT]: 2024-05-26 09:26:58 Age [y:d:h:m:s]: 00:158:06:00:07
Block: 1030338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113264 RingCT/type: yes/0
Extra: 0108470d2c98b5be6770a4841f6231b339805b79f9158745c136537da5a0c77665021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff5f808f2c899c9a6db3c93e3d4427e76ebd765e9b31eea46105fee7c92e46bb 0.600000000000 1498593 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": 1030348, "vin": [ { "gen": { "height": 1030338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff5f808f2c899c9a6db3c93e3d4427e76ebd765e9b31eea46105fee7c92e46bb" } } ], "extra": [ 1, 8, 71, 13, 44, 152, 181, 190, 103, 112, 164, 132, 31, 98, 49, 179, 57, 128, 91, 121, 249, 21, 135, 69, 193, 54, 83, 125, 165, 160, 199, 118, 101, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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