Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7142d11f3b13effa5c5ac716dfaf6b417430fd6b59b241df38318419c8e1afaf

Tx prefix hash: 240d7e72d8a3479b0918f9cd22fc1e7d6e87237825a10fe9929b0ebaeb7973b2
Tx public key: 0bcf41a8ffa9f2badce786a6aff8760537292c85ab609ea20e43a0a7619e4584
Timestamp: 1737717914 Timestamp [UCT]: 2025-01-24 11:25:14 Age [y:d:h:m:s]: 00:049:11:58:26
Block: 1204244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35200 RingCT/type: yes/0
Extra: 010bcf41a8ffa9f2badce786a6aff8760537292c85ab609ea20e43a0a7619e45840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66fba0f2c9dbdfea610e96d4b31ebcbe3fc15b8fbce2cf3e215be94e3d5ce4bf 0.600000000000 1690929 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": 1204254, "vin": [ { "gen": { "height": 1204244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66fba0f2c9dbdfea610e96d4b31ebcbe3fc15b8fbce2cf3e215be94e3d5ce4bf" } } ], "extra": [ 1, 11, 207, 65, 168, 255, 169, 242, 186, 220, 231, 134, 166, 175, 248, 118, 5, 55, 41, 44, 133, 171, 96, 158, 162, 14, 67, 160, 167, 97, 158, 69, 132, 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