Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 642d0e96fb01f8aad4e3235216df7f5b4c63bc2ee389876d88ecb570890f85a4

Tx prefix hash: 839760816c448ac153f86ecc84bf49fd58751536a9f1e531a76afcdcec34dcc7
Tx public key: 4ba7fdb04d23b2c6ff69e8f001b78ea6fa1e118968cac65d2422c18040788f32
Timestamp: 1737746456 Timestamp [UCT]: 2025-01-24 19:20:56 Age [y:d:h:m:s]: 00:048:20:41:18
Block: 1204481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34751 RingCT/type: yes/0
Extra: 014ba7fdb04d23b2c6ff69e8f001b78ea6fa1e118968cac65d2422c18040788f320211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 967816b332615a5b6cb73803ead1c25c5253d78c796f50230b2a7e1f6c3b855e 0.600000000000 1691168 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": 1204491, "vin": [ { "gen": { "height": 1204481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "967816b332615a5b6cb73803ead1c25c5253d78c796f50230b2a7e1f6c3b855e" } } ], "extra": [ 1, 75, 167, 253, 176, 77, 35, 178, 198, 255, 105, 232, 240, 1, 183, 142, 166, 250, 30, 17, 137, 104, 202, 198, 93, 36, 34, 193, 128, 64, 120, 143, 50, 2, 17, 0, 0, 0, 6, 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