Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f59fcfa6194e636d3462c74ef95afbf885299b2131eba9e1c07c4ef5e72ce697

Tx prefix hash: 7373336ae11b4c12662e480d794320319f77122410810476f9728543b174670c
Tx public key: 7e618b6b25a362b593d2c37da3d97f9705d0b571d9457df1d933d276378156b0
Timestamp: 1735481523 Timestamp [UCT]: 2024-12-29 14:12:03 Age [y:d:h:m:s]: 00:117:22:44:32
Block: 1185763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84118 RingCT/type: yes/0
Extra: 017e618b6b25a362b593d2c37da3d97f9705d0b571d9457df1d933d276378156b00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96df55ab53d5dba3eeb210cea68511f8b66861fd5cb29e7467f4c1f88f4a318f 0.600000000000 1672238 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": 1185773, "vin": [ { "gen": { "height": 1185763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96df55ab53d5dba3eeb210cea68511f8b66861fd5cb29e7467f4c1f88f4a318f" } } ], "extra": [ 1, 126, 97, 139, 107, 37, 163, 98, 181, 147, 210, 195, 125, 163, 217, 127, 151, 5, 208, 181, 113, 217, 69, 125, 241, 217, 51, 210, 118, 55, 129, 86, 176, 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