Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999d3e0c7f942035486319f9596074c33641156fc7cc69ff617a4aa8db93a0e4

Tx prefix hash: 618177d036afb06197103d1eae1e933335bbb9beaf63f84fd7c32f9dbee35322
Tx public key: c715bdcc5f2f54dc63269040b5b9d23ba49fec22c20b9a2b227fe43179eec8d4
Timestamp: 1730094563 Timestamp [UCT]: 2024-10-28 05:49:23 Age [y:d:h:m:s]: 00:062:12:44:58
Block: 1141171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44729 RingCT/type: yes/0
Extra: 01c715bdcc5f2f54dc63269040b5b9d23ba49fec22c20b9a2b227fe43179eec8d4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09e65de86213b32ace47c339e8934cc5e3a046d137f1fc4fd49e89124cb708a8 0.600000000000 1624978 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": 1141181, "vin": [ { "gen": { "height": 1141171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09e65de86213b32ace47c339e8934cc5e3a046d137f1fc4fd49e89124cb708a8" } } ], "extra": [ 1, 199, 21, 189, 204, 95, 47, 84, 220, 99, 38, 144, 64, 181, 185, 210, 59, 164, 159, 236, 34, 194, 11, 154, 43, 34, 127, 228, 49, 121, 238, 200, 212, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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