Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7022b30d9249c48f637f1ccd6cff91079694d8d732b90f5ee436889d9683dc24

Tx prefix hash: 392acfb7bca1b8d7f45f4c018a9c932f4fb08e6fb477abbcb7ea1b798b904113
Tx public key: a4ab3ee947ea36ae1229665d2c41f94bf02e3ee56cfd56d2644c4bec429f3dd9
Timestamp: 1739930278 Timestamp [UCT]: 2025-02-19 01:57:58 Age [y:d:h:m:s]: 00:232:01:39:18
Block: 1222310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163594 RingCT/type: yes/0
Extra: 01a4ab3ee947ea36ae1229665d2c41f94bf02e3ee56cfd56d2644c4bec429f3dd90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9987fbd0d14d082ea78adfd0a00bf6578df42739f9aefea6e540f45abd81871 0.600000000000 1709161 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": 1222320, "vin": [ { "gen": { "height": 1222310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9987fbd0d14d082ea78adfd0a00bf6578df42739f9aefea6e540f45abd81871" } } ], "extra": [ 1, 164, 171, 62, 233, 71, 234, 54, 174, 18, 41, 102, 93, 44, 65, 249, 75, 240, 46, 62, 229, 108, 253, 86, 210, 100, 76, 75, 236, 66, 159, 61, 217, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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