Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66227bf219465286d81d5006ecb3e2387a2ca0d07c793143b72b93ef0872f603

Tx prefix hash: f48f12bc9c988d373c0391ba8740ce82b7baa3e973997f838cd0b5323e25bca2
Tx public key: 894da9d9b7c179d01a1772f495bba625c0f1adfa74ea47d229dc81908f3044a8
Timestamp: 1710186845 Timestamp [UCT]: 2024-03-11 19:54:05 Age [y:d:h:m:s]: 01:265:12:36:42
Block: 976211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448510 RingCT/type: yes/0
Extra: 01894da9d9b7c179d01a1772f495bba625c0f1adfa74ea47d229dc81908f3044a80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f878a4b50a1e6315a679b25960f6e607dd9753d20d6fc3f76d177d80ba5f013d 0.600000000000 1436202 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": 976221, "vin": [ { "gen": { "height": 976211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f878a4b50a1e6315a679b25960f6e607dd9753d20d6fc3f76d177d80ba5f013d" } } ], "extra": [ 1, 137, 77, 169, 217, 183, 193, 121, 208, 26, 23, 114, 244, 149, 187, 166, 37, 192, 241, 173, 250, 116, 234, 71, 210, 41, 220, 129, 144, 143, 48, 68, 168, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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