Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fb35fa257475ae2bdd4cd3ae68b640f262cc0dc0a75bee6b01242c46c2b93be

Tx prefix hash: 5a6354c4ebaf9ec15cfd2d4ed9c27e45cb92e61cba2138d118b2a38db963a48e
Tx public key: bc0dc8c864dcf4d255d7e3bf4ec0455864e50c4bd0a6df0e4fb00278b83a18ab
Timestamp: 1736276988 Timestamp [UCT]: 2025-01-07 19:09:48 Age [y:d:h:m:s]: 00:083:01:36:17
Block: 1192358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59151 RingCT/type: yes/0
Extra: 01bc0dc8c864dcf4d255d7e3bf4ec0455864e50c4bd0a6df0e4fb00278b83a18ab0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e808036a3c16010cf9b24fdedf31f22654e489777b5d0a1a63a4526ff68db0d8 0.600000000000 1678907 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": 1192368, "vin": [ { "gen": { "height": 1192358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e808036a3c16010cf9b24fdedf31f22654e489777b5d0a1a63a4526ff68db0d8" } } ], "extra": [ 1, 188, 13, 200, 200, 100, 220, 244, 210, 85, 215, 227, 191, 78, 192, 69, 88, 100, 229, 12, 75, 208, 166, 223, 14, 79, 176, 2, 120, 184, 58, 24, 171, 2, 17, 0, 0, 0, 2, 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