Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da0fc5d22a7f3322e7eea4abab6b2e6e8544b7a8f732477c2dbf79bffd837cb5

Tx prefix hash: ebc3d39e6f5f8d331dad684eaacae4af3a1f497768ba650c526e6b5d23b46b02
Tx public key: c07886cc9a29832ae7411e40ab90469d6a8a790684dd57842d7df81bf7006154
Timestamp: 1745187700 Timestamp [UCT]: 2025-04-20 22:21:40 Age [y:d:h:m:s]: 00:259:03:10:45
Block: 1265847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183009 RingCT/type: yes/0
Extra: 01c07886cc9a29832ae7411e40ab90469d6a8a790684dd57842d7df81bf70061540211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38a6aae4792b933359f71f1ed8d8ce6344c9eedcda2cb9cc3ca8e3a4f6795c16 0.600000000000 1753060 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": 1265857, "vin": [ { "gen": { "height": 1265847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38a6aae4792b933359f71f1ed8d8ce6344c9eedcda2cb9cc3ca8e3a4f6795c16" } } ], "extra": [ 1, 192, 120, 134, 204, 154, 41, 131, 42, 231, 65, 30, 64, 171, 144, 70, 157, 106, 138, 121, 6, 132, 221, 87, 132, 45, 125, 248, 27, 247, 0, 97, 84, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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